-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
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
CIDv1 link specifications do not work ( hardcoded mdag expectation somewhere ) #3427
Comments
Do you mind pasting the commands you used to generate the objects in question? |
@whyrusleeping There is no command I can currently share. As I said previously these are all experiments of mine trying to figure out how I can use ipfs for my own needs, entirely outside of go-ipfs, but remaining compatible with it (i.e. having I am essentially assembling all the bytes by hand, and then feeding them to |
okay, can you provide a set of commands like:
That recreate each object? |
Sure thing:
Killing daemon, restarting with
|
@whyrusleeping in #3431 you said:
Surely this issue is the same then? Even though the |
@mib-kd743naq With block put, we never create a protobuf node, so at least here, we should be putting the right CID to disk, this issue is subtly different (but likely a very similar problem in any case) |
@mib-kd743naq can you verify that this was fixed in latest master? |
Works as of 0c413de |
Version information:
Type:
Bug
Priority:
P4
Description:
Full description at https://ipfs.io/ipfs/QmXUmGtjEKnceju74LDStC24DDmJWxnxdH7aQPLYk9zJe5
The text was updated successfully, but these errors were encountered: