-
-
Notifications
You must be signed in to change notification settings - Fork 31.8k
GH-110894: Call loop exception handler for exceptions in client_connected_cb #111601
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
kumaraditya303
commented
Nov 1, 2023
•
edited by bedevere-app
bot
Loading
edited by bedevere-app
bot
- Issue: Asyncio stream doesn't handle exceptions in callback #110894
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, good fix!
Thanks @kumaraditya303 for the PR 🌮🎉.. I'm working now to backport this PR to: 3.11, 3.12. |
Sorry, @kumaraditya303, I could not cleanly backport this to
|
Sorry, @kumaraditya303, I could not cleanly backport this to
|
GH-111632 is a backport of this pull request to the 3.12 branch. |
… client_connected_cb (pythonGH-111601) Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.. (cherry picked from commit 229f44d) Co-authored-by: Kumar Aditya <kumaraditya@python.org>
|
|
… client_connected_cb (pythonGH-111601) Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.. (cherry picked from commit 229f44d) Co-authored-by: Kumar Aditya <kumaraditya@python.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
The test fails on many buildbots: see previous comments and issue #111644. |
…_connected_cb (python#111601) Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.
@kumaraditya303 Please revert this ASAP. CI is failing on main, meaning we cannot merge bug fixes for other issues. |
I fixed the issue with PR #111713. Sadly, on existing PRs, either failing jobs should be re-run, or the PR should be rebased on the main branch.
@kumaraditya303: Do you plan to backport the change to 3.11? If yes, please include my fix in your backport ;-) |
Oh, PR #111634 already exists. I included my fix in this backport. |
…n client_connected_cb (GH-111601) (GH-111632) (#111634) * [3.12] GH-110894: Call loop exception handler for exceptions in client_connected_cb (GH-111601) (GH-111632) (cherry picked from commit 9aa8829) Co-authored-by: Kumar Aditya <kumaraditya@python.org> Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.. (cherry picked from commit 229f44d) * gh-111644: Fix asyncio test_unhandled_exceptions() (#111713) Fix test_unhandled_exceptions() of test_asyncio.test_streams: break explicitly a reference cycle. Fix also StreamTests.tearDown(): the loop must not be closed explicitly, but using set_event_loop() which takes care of shutting down the executor with executor.shutdown(wait=True). BaseEventLoop.close() calls executor.shutdown(wait=False). (cherry picked from commit ac01e22) --------- Co-authored-by: Kumar Aditya <kumaraditya@python.org> Co-authored-by: Victor Stinner <vstinner@python.org>
…_connected_cb (python#111601) Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.
…_connected_cb (python#111601) Call loop exception handler for exceptions in `client_connected_cb` of `asyncio.start_server` so that applications can handle it.