Fix large inner files with PAX format #36
Merged
Conversation
This file contains 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
bdraco
force-pushed
the
fix_large_inner_files_pax
branch
2 times, most recently
from
6a39f82 to
a1ebeb4
Compare
bdraco
force-pushed
the
fix_large_inner_files_pax
branch
from
a1ebeb4 to
0781191
Compare
agners
reviewed
Feb 26, 2024
agners
reviewed
Feb 26, 2024
Co-authored-by: Stefan Agner <[email protected]>
agners
approved these changes
Feb 26, 2024
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.
If the file size is larger than 12 digits tarfile writes a larger header when using PAX. Since we can't set the size to anything other than 0 initially (in case the inner tar creation raise), we set the mtime to a float to ensure we get a PAX header
fixes home-assistant/supervisor#4924