-
Notifications
You must be signed in to change notification settings - Fork 26
Introduce OCI image unpack feature #381
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
henrybear327
wants to merge
5
commits into
sysprog21:main
Choose a base branch
from
henrybear327:oci/unpack
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
Show all changes
5 commits
Select commit
Hold shift + click to select a range
c08f68c
Remove replaceFile's per-branch cleanup calls
henrybear327 7075d89
Extract checkLayout, checkJSON, and nestedIndex
henrybear327 e2a1dcd
Add a store read path and rootfs cache
henrybear327 f4fa70d
Add unpack for stored OCI images
henrybear327 2a39064
Document unpacking OCI images
henrybear327 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
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
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.
P3: When a tarEntry has an empty Name with Type==0 and Link=="",
e.Name[len(e.Name)-1]indexes index -1 and panics the test. Guard for the empty Name before indexing, or produce a clear t.Fatal.Prompt for AI agents
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.
Is the issue still valid? Why?
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.
@henrybear327 Yes, it still stands as a code-level hazard, though it's defensive rather than something the current tests hit.
The switch is unchanged in the current file: when
e.Type == 0ande.Link == ""(both the zero values), control falls tocase e.Name[len(e.Name)-1] == '/', andtarEntry{Name: ""}(a plain body with no type/link) indexes[-1]and panics. Every call site in the current suite passes a non-emptyName, so it won't fire today — but the helper's contract doesn't enforce that, and a future test author adding an entry with just aBody(the struct's most natural bare use) would get a confusing index-out-of-range panic instead of a clear message.Cheapest fix is to make the empty case explicit before the indexing, e.g.:
That preserves the existing behavior for real entries and turns the footgun into a readable failure. I'd keep it as P3 either way.
Tip: get faster answers by chatting with cubic’s review copilot in the review UI