multi: do no expire a blocked transfer #17639
Closed
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
When checking to expire a transfer with input data pending, also assess the blocked status and do not EXPIRE_RUN_NOW a transfer that is blocked on READ/WRITE.
vszakats
approved these changes
Jun 17, 2025
|
Thank you! (I tagged as a follow-up) |
denandz
pushed a commit
to denandz/curl
that referenced
this pull request
Jun 21, 2025
When checking to expire a transfer with input data pending, also assess the blocked status and do not EXPIRE_RUN_NOW a transfer that is blocked on READ/WRITE. Follow-up to 62349e4 curl#17636 Closes curl#17639
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.
When checking to expire a transfer with input data pending, also assess the blocked status and do not EXPIRE_RUN_NOW a transfer that is blocked on READ/WRITE.
Follow-up to 62349e4 #17636