Skip to content
This repository has been archived by the owner on Oct 5, 2023. It is now read-only.

v0.6.0 Routing API errors #182

Closed
avislash opened this issue Jun 12, 2023 · 3 comments
Closed

v0.6.0 Routing API errors #182

avislash opened this issue Jun 12, 2023 · 3 comments

Comments

@avislash
Copy link

After upgrading to go-ipfs-http-client v0.6.0 I recieve the following errors when attemping to run my program

# github.com/ipfs/go-ipfs-http-client
../../go/pkg/mod/github.com/ipfs/[email protected]/api.go:214:9: cannot use (*RoutingAPI)(api) (value of type *RoutingAPI) as iface.RoutingAPI value in return statement: *RoutingAPI does not implement iface.RoutingAPI (wrong type for method Put)
                have Put(context.Context, string, []byte) error
                want Put(context.Context, string, []byte, ...options.RoutingPutOption) error
../../go/pkg/mod/github.com/ipfs/[email protected]/dag.go:37:16: undefined: format.DefaultBlockDecoder
../../go/pkg/mod/github.com/ipfs/[email protected]/pin.go:204:16: cannot use &pinVerifyRes{…} (value of type *pinVerifyRes) as iface.PinStatus value in send: *pinVerifyRes does not implement iface.PinStatus (missing method Err)
@avislash avislash added the need/triage Needs initial labeling and prioritization label Jun 12, 2023
@welcome
Copy link

welcome bot commented Jun 12, 2023

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

  • "Priority" labels will show how urgent this is for the team.
  • "Status" labels will show if this is ready to be worked on, blocked, or in progress.
  • "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

@aschmahmann
Copy link
Contributor

This repo is being moved into kubo as discussed in ipfs/kubo#9124. The latest version of kubo master has client/rpc which is where this code has been moved.

There will be a kubo v0.21.0-rc1 later this week that you can use. Note that once this release is out the plan is to merge #180 (which will forward all types, etc. from this repo to kubo) and then archive this repo.

cc @Jorropo

@lidel lidel added status/blocked Unable to be worked further until needs are met and removed need/triage Needs initial labeling and prioritization labels Jun 12, 2023
@lidel
Copy link
Member

lidel commented Jul 10, 2023

@avislash Kubo 0.21.0 released, please upgrade, and switch to RPC client from https://github.com/ipfs/kubo/tree/master/client/rpc and if the problem is still present, fill an issue in that repo.

@lidel lidel closed this as not planned Won't fix, can't repro, duplicate, stale Jul 10, 2023
@aschmahmann aschmahmann removed the status/blocked Unable to be worked further until needs are met label Jul 17, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants