-
Notifications
You must be signed in to change notification settings - Fork 5
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
Paths not resolvable within directories don't return the directory #84
Comments
Here's one with one level of nesting that does something similar, although it returns the first block, just not the inner block that would show that the final path segment doesn't exist: We get |
Hopefully fixed by storacha/dagula#32 |
For: $ curl -v -H 'Accept: application/vnd.ipld.car;version=1;order=dfs;dups=y' 'https://dag.w3s.link:443/ipfs/bafybeihvvamsgstvslmn5drnu5chyeejxb3jp5zjtykn6ftdkhas3oakem/metadata/1201' -o w3s.car We now get:
|
For: $ curl -v -H 'Accept: application/vnd.ipld.car;version=1;order=dfs;dups=y' 'https://dag.w3s.link:443/ipfs/bafybeigyzfjunykku7smhml652rahobne7fsq7fokg22idwmwxpc5b7z64/1472?dag-scope=entity' -o w3s.car We now get:
|
Perhaps the inversion of #83. One failure that I think is repeated in different forms is a path through a directory that doesn't contain that path returns an empty CAR but it should (again, "should" here being arguable, this is undefined behaviour according to IPIP-402) just return the block so you can trustlessly prove that the path is unresolveable.
bafybeigyzfjunykku7smhml652rahobne7fsq7fokg22idwmwxpc5b7z64
is one of the most common ones in the last ~day, ending in lots of different integer paths, such as/1472
. The directory contains integer paths, but its the ones that don't exist that return an empty CAR:Results in a CAR with just the header.
Results in a CAR with 2 blocks, root and the block referenced by the named link "3001".
The text was updated successfully, but these errors were encountered: