Repository navigation
Conversation
…omplete extraction
…ith invalid PAX header 'size'
ptim0626
force-pushed
the
extract-despite-invalid-pax-size
branch
from
November 9, 2026 09:53
526c0fb to
0dc4a15
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
In this PR, I limit the invalid PAX header to be ignored to
sizeonly.uid/gid/atime/mtimecan be similarly handled if this approach is appropriate and fits within the scope of this PR. Parsing of similar PAX headers are grouped together now, i.e.GNU.sparse.name/pathandGNU.sparse.size/GNU.sparse.realsize/size.