AsyncThrowingBackpressureStream Cancellation
#262
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
dimitribouniol
changed the title
AsyncThrowingBackpressureStream would not reac…AsyncThrowingBackpressureStream Cancellation
…t to cancellation properly
dimitribouniol
force-pushed
the
dimitri/backpressure-cancellation
branch
from
0dc39d2 to
5e04043
Compare
…itialize when a suspended write was never read
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.
Fixed an issue where
AsyncThrowingBackpressureStreamwould not react to cancellation properly, often leading to the provider task not being cancelled. This caused ranged reads in an already cancelled task to suspend indefinitely.