Repository navigation
Keep negative-size range-stream reads within the selected range - #677
Merged
Merged
Conversation
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.
Summary
Reading a range stream with a negative size (e.g.
read(-1)) returned bytes past the end of the configured range, because the negative size was passed straight to the inner stream. This clamps a negative size to the remaining range length.Changes
RangeOfInputStream(b2sdk/_internal/stream/range.py).Verification
python -m pytest test/unit/stream— 7 passedSupersedes the stale draft #633 (same one-line clamp); #633 can be closed.