We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Actual:
# ipfs resolve /ipfs/bafkreickb4yq3sr3q2xqn3z3wzimilsa4wkbx25azqbvcnihq65moyjcvi /ipfs/zb2rhbdNoGAYtRfZgcobnk5bJWTrqZY18zZ2o3dmp4QD12mxV
Expected:
# ipfs resolve /ipfs/bafkreickb4yq3sr3q2xqn3z3wzimilsa4wkbx25azqbvcnihq65moyjcvi /ipfs/bafkreickb4yq3sr3q2xqn3z3wzimilsa4wkbx25azqbvcnihq65moyjcvi
It forgets the base32 encoding and applies base58btc instead.
Part of ipfs/ipfs#337 (cc @kyledrake)
The text was updated successfully, but these errors were encountered:
This is going to be so painful...
Sorry, something went wrong.
This ended up being fairly easy to do #5289 now respects the CID in ipfs resolve.
ipfs resolve
However, other similar cases such of ipfs pin are not so easy. As a solution to that I present ipfs/go-cid#64.
ipfs pin
kevina
Successfully merging a pull request may close this issue.
Version information: 0.4.16
Type: bug
Description:
Actual:
Expected:
It forgets the base32 encoding and applies base58btc instead.
Part of ipfs/ipfs#337 (cc @kyledrake)
The text was updated successfully, but these errors were encountered: