-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
asyncio internals throw RuntimeError: Event loop is closed
on script exit
#92841
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
Labels
Comments
zooba
pushed a commit
that referenced
this issue
May 17, 2022
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 17, 2022
…honGH-92842) (cherry picked from commit 33880b4) Co-authored-by: Oleg Iarygin <oleg@arhadthedev.net>
miss-islington
pushed a commit
to miss-islington/cpython
that referenced
this issue
May 17, 2022
…honGH-92842) (cherry picked from commit 33880b4) Co-authored-by: Oleg Iarygin <oleg@arhadthedev.net>
miss-islington
added a commit
that referenced
this issue
May 17, 2022
Thanks, seems like we can close this one out |
Oh never mind, the 3.10 backport hasn't been merged |
This was referenced Jun 30, 2022
3 tasks
wookayin
added a commit
to wookayin/pynvim
that referenced
this issue
Oct 15, 2023
python < 3.10.6 has a bug on proactor-based pipe transport: when a `_ProactorBasePipeTransport` instance is garbage-collected (usually after the associated event loop is closed), it will raise an error. For older versions of python, we apply the same monkey-patchin to suppress warnings (actually these are errors). Ref: python/cpython#83413 and python/cpython#92841 CI output (pytest warnings): ``` ======================= 71 passed, 66 warnings in 6.55s ======================= Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x0000021A9534F700> Traceback (most recent call last): File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\proactor_events.py", line 115, in __del__ _warn(f"unclosed transport {self!r}", ResourceWarning, source=self) File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\proactor_events.py", line 79, in __repr__ info.append(f'fd={self._sock.fileno()}') File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\windows_utils.py", line 102, in fileno raise ValueError("I/O operation on closed pipe") ValueError: I/O operation on closed pipe Exception ignored in: <function _ProactorBasePipeTransport.__del__ at 0x0000021A9534F700> Traceback (most recent call last): File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\proactor_events.py", line 115, in __del__ File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\proactor_events.py", line 79, in __repr__ File "C:\hostedtoolcache\windows\Python\3.8.10\x64\lib\asyncio\windows_utils.py", line 102, in fileno ValueError: I/O operation on closed pipe ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Actual behavior
This issue was reported in aio-libs/aiohttp#4324 so the reproducer is copied from there.
Expected behavior
Normal exit without termination. There is no user-created loop to be closed manually.
Your environment
The text was updated successfully, but these errors were encountered: