Fix EOF handling of __archive_read_ahead #2196
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
Reaching EOF for first time sets the correct amount of available bytes, but each subsequent call returns 0. Do not forget that the copy buffer can already contain data and return the amount of bytes left in there. See added test case.
kientzle
approved these changes
Jun 2, 2024
|
Nice fix! Thank you for the careful test case. |
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.
Reaching EOF for first time sets the correct amount of available bytes, but each subsequent call returns 0.
Do not forget that the copy buffer can already contain data and return the amount of bytes left in there.
See added test case.