[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by robbiecares : -- nosy: +robbiecares ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset 40e2444c364eede59f193979df5a02ed958f56e9 by Miss Islington (bot) in branch '3.8': bpo-39010: Improve test shutdown (GH-22066) (#22083) https://github.com/python/cpython/commit/40e2444c364eede59f193979df5a02ed958f56e9 --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset 8d68e59f11267ded765d4af6d71a49784a12fad5 by Miss Islington (bot) in branch '3.9': bpo-39010: Improve test shutdown (GH-22066) (#22082) https://github.com/python/cpython/commit/8d68e59f11267ded765d4af6d71a49784a12fad5 --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by miss-islington : -- pull_requests: +21169 pull_request: https://github.com/python/cpython/pull/22083 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by miss-islington : -- pull_requests: +21168 pull_request: https://github.com/python/cpython/pull/22082 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset a986b061a3cd4661eb9f857e2936291f1847bd15 by Miss Islington (bot) in branch '3.8': bpo-39010: Fix errors logged on proactor loop restart (GH-22017) (#22035) https://github.com/python/cpython/commit/a986b061a3cd4661eb9f857e2936291f1847bd15

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset 49571c0b0e57e20d85727c738d9a0fe342dd2938 by Miss Islington (bot) in branch '3.9': bpo-39010: Fix errors logged on proactor loop restart (GH-22017) (#22034) https://github.com/python/cpython/commit/49571c0b0e57e20d85727c738d9a0fe342dd2938

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset be435ae2b064dc64f04475bec632862e1dbf605f by Ben Darnell in branch 'master': bpo-39010: Improve test shutdown (#22066) https://github.com/python/cpython/commit/be435ae2b064dc64f04475bec632862e1dbf605f --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Ben Darnell added the comment: I've fixed the test and added some commentary about the different levels of clean shutdown we must do to quiet all the warnings: https://github.com/python/cpython/pull/22066 -- ___ Python tracker

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Ben Darnell : -- pull_requests: +21156 pull_request: https://github.com/python/cpython/pull/22066 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

David Bolen added the comment: I'm guessing the warning appears odd as we're seeing a thread shutdown data race. The message is produced by threading_cleanup in support/threading_helper.py, and it appears that between the first and second lines one of the initially dangling threads goes

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Ben Darnell added the comment: I can confirm that those warnings appear to be coming from the test I added here. I'm not sure how to interpret them, though - what does it mean for the main thread to be dangling? -- ___ Python tracker

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

David Bolen added the comment: I've been seeing failures on the Win10 buildbot 3.x branch that seem to correlate with the timing of this change - could there be some further work needed on Windows? Or, if it's a test-only artifact and the warnings are innocuous, something to ignore the

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Steve Dower added the comment: Thanks, Ben! -- ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Yury Selivanov added the comment: New changeset ea5a6363c3f8cc90b7c0cc573922b10f296073b6 by Ben Darnell in branch 'master': bpo-39010: Fix errors logged on proactor loop restart (#22017) https://github.com/python/cpython/commit/ea5a6363c3f8cc90b7c0cc573922b10f296073b6 --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by miss-islington : -- pull_requests: +21133 pull_request: https://github.com/python/cpython/pull/22035 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by miss-islington : -- nosy: +miss-islington nosy_count: 11.0 -> 12.0 pull_requests: +21132 pull_request: https://github.com/python/cpython/pull/22034 ___ Python tracker

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Ben Darnell added the comment: I've posted a pull request with a test and fix: https://github.com/python/cpython/pull/22017. It's a more targeted fix than cmeyer's PR (which I didn't even notice until now due to unfamiliarity with the BPO UI) --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Ben Darnell : -- pull_requests: +21117 pull_request: https://github.com/python/cpython/pull/22017 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Steve Dower added the comment: Any input from the asyncio experts? I don't have an issue with handling the exception in this case, and hopefully when someone is up to the task of dealing with the range of edge cases throughout this loop implementation, hopefully they can get the ordering of

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Chris Meyer : -- keywords: +patch pull_requests: +19769 stage: -> patch review pull_request: https://github.com/python/cpython/pull/20525 ___ Python tracker ___

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Burak Yiğit Kaya : -- nosy: +Burak Yiğit Kaya ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Chris Meyer added the comment: Here is another way to reproduce this (or an extremely similar) error without a loop. Since may be a race condition, I'm not sure this works 100% of the time on all machines - but it did on several machines I tried. ``` import asyncio loop =

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Segev Finer : -- nosy: +Segev Finer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Chris Meyer : -- nosy: +cmeyer ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Peter Lovett : -- nosy: +PeterL777 ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Rustam S. added the comment: Please take a look at this as well: (ipython #12049 'Unhandled exception in event loop' (WinError 995)) https://github.com/ipython/ipython/issues/12049#issuecomment-586544339 and below -- nosy: +Rustam S. ___ Python

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Ben Darnell added the comment: I just spent some time digging into this. Each call to `run_forever` starts a call to `_loop_self_reading`, then attempts to cancel it before returning:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by Caleb Hattingh : -- nosy: +cjrh ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Change by STINNER Victor : -- nosy: -vstinner ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Jonathan Slenders added the comment: Even simpler, the following code will crash after so many iterations: ``` import asyncio loop = asyncio.get_event_loop() while True: loop.call_soon_threadsafe(loop.stop) loop.run_forever() ``` Adding a little sleep of 0.01s after `run_forever()`

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Jonathan Slenders added the comment: It looks like the following code will reproduce the issue: ``` import asyncio import threading loop = asyncio.get_event_loop() while True: def test(): loop.call_soon_threadsafe(loop.stop) threading.Thread(target=test).start()

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Jonathan Slenders added the comment: Thanks Victor for the reply. It looks like it's the self-socket in the BaseProactorEventLoop that gets closed. It's exactly this FD for which the exception is raised. We don't close the event loop anywhere. I also don't see `_close_self_pipe` being

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

STINNER Victor added the comment: ConnectionResetError means that the pipe socket is closed. Was the event loop closed? Can you provide a reproducer? Can you try to get debug logs to see what's going on? https://docs.python.org/dev/library/asyncio-dev.html#debug-mode -- nosy:

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

Jonathan Slenders added the comment: Suppressing `ConnectionResetError` in `BaseProactorEventLoop._loop_self_reading`, like we do with `CancelledError` seems to fix it. Although I'm not sure what it causing the error, and whether we need to handle it somehow. --

[issue39010] ProactorEventLoop raises unhandled ConnectionResetError

New submission from Jonathan Slenders : We have a snippet of code that runs perfectly fine using the `SelectorEventLoop`, but crashes *sometimes* using the `ProactorEventLoop`. The traceback is the following. The exception cannot be caught within the asyncio application itself (e.g., it is