-
Notifications
You must be signed in to change notification settings - Fork 0
Decode container entries in DAG-JSON output #20
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
Open
bajtos
wants to merge
1
commit into
main
Choose a base branch
from
feat/view-container-json-entries
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I asked Claude to explain this breaking change:
The
| jqin the README is cosmetic — the tool prints one line either way, jq just pretty-prints it. Not a change.The entry shape is a breaking change.
.["ctn-v1"][N] was {"/":{"bytes":"…"}}and is now[sig, {tag: payload}]. Verified consequence:old output → container.UnmarshalDagJSON:
new output → container.UnmarshalDagJSON: expected object open but read [
There's a second problem underneath it.
--jsonis documented as "the dag-json encoding of the input", and for a container the ctn-v1 field genuinely is a list of byte strings. So the new output is valid DAG-JSON but it is not the DAG-JSON encoding of the container. My change quietly redefines what the flag means, and the mixed-shape array (token envelope or raw bytes) is a wart that only exists because of that redefinition.Worth noting the entry-source fix is separable and not breaking on its own: reading entries from the input instead of the roundtrip fixes the order, the count and the -i disagreement while keeping the byte-string shape.