Repository navigation
fix(sync): survive an exception raised by a signal handler during a sync call - #3230
Merged
Pavel Feldman (pavelfeldman) merged 1 commit intoOct 8, 2026
Merged
Conversation
Pavel Feldman (pavelfeldman)
force-pushed
the
fix-3222
branch
from
October 8, 2026 17:49
fb6bd25 to
df91ddb
Compare
Yury Semikhatsky (yury-s)
approved these changes
Oct 8, 2026
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
2 participants
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
signalmethod) while a sync call waits lands inside the dispatcher greenlet and ends it. The dispatcher now hands the exception to the waiting user greenlet, stays alive and runs the loop again on the next call.wait_for_futureowns the resume callback and removes it when a wait is abandoned, so the cancelled call cannot resume the user greenlet later.Fixes #3222