-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
ipfs object diff is buggy for links with the same name. #7044
Comments
I think we did some work toward fixing this. I can take another look at this but note we are aiming to deprecate the |
Looking into this. |
We indeed do not process correctly unnamed links, see I'll need confirmation from someone in the team about:
|
IDK if it is in use, but I was going to use it but since it doesn't work I found another solution. On the other hand if it doesn't work probably no one uses it. But it would be nice if there was a solution that did work. |
Yes, the main issue is that we're planning on deprecating the |
We did deprecate |
Version information:
Description:
TL;DR when diffing all links on the LHS are compared to the first link with the same name on the RHS.
All blocks in the LHS are apparently replaced with the first block of the RHS.
File reporting no diff.
The setup is to create a file with all blocks identical. In this example I created a file with two all-zero blocks.
Then you create a second file with the first block matching and anything else after that. Note that not even the number of blocks or the size of the blocks or files matter. As long as the first block matches
ipfs object diff
will report no diff.Suggestions.
Data
field as well as theLinks
.Other concerns.
The output is ambiguous when the links have no names. Something should be done to make this explicit.
The text was updated successfully, but these errors were encountered: