-
Notifications
You must be signed in to change notification settings - Fork 43
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
fix: (#33) Rare combination of settings could lead to writing a corrupt archive with overlength extra data, and data_start locations when reading the archive back were also wrong #221
Merged
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
Pr0methean
added
the
waiting to be automatically merged
If this PR isn't automatically merged, suspect a broader issue.
label
Jul 20, 2024
Pr0methean
added
help wanted
Extra attention is needed
Please fix failing tests
Tests are failing with this change; please fix them.
and removed
waiting to be automatically merged
If this PR isn't automatically merged, suspect a broader issue.
labels
Jul 20, 2024
# Conflicts: # src/read.rs # src/write.rs
github-merge-queue
bot
removed this pull request from the merge queue due to a conflict with the base branch
Jul 28, 2024
Signed-off-by: Chris Hennick <[email protected]>
Pr0methean
changed the title
fix: Rare combination of settings could lead to writing a corrupt archive with overlength extra data
fix: (#33) Rare combination of settings could lead to writing a corrupt archive with overlength extra data or reading back the data_start location incorrectly
Jul 28, 2024
Pr0methean
changed the title
fix: (#33) Rare combination of settings could lead to writing a corrupt archive with overlength extra data or reading back the data_start location incorrectly
fix: (#33) Rare combination of settings could lead to writing a corrupt archive with overlength extra data, and data_start locations when reading the archive back were also wrong
Jul 29, 2024
This was referenced Jul 29, 2024
Closed
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
help wanted
Extra attention is needed
Please fix failing tests
Tests are failing with this change; please fix them.
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.
The reason this PR is so big is because we're changing how the total extra-data size is counted and how the extra data is stored; previously it didn't include the ZIP64 header or alignment padding, but now it does.