-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
RuntimeError: File descriptor 2877 is used by transport <TCPTransport closed=False reading=True 0x55b8dc9baa90> #10362
Comments
Never seen that before. Potential compatibility issue between aiohappyeyeballs and uvloop, @bdraco? |
Known issue with uvloop. See MagicStack/uvloop#646 |
Make sure you have the latest aiohappyeyeballs as it reduces the chance the problem can happen, however ultimately it's a problem uvloop will have to fix. |
You can also further reduce the risk of the problem happening in uvloop by disabling happyeyeballs on the connector. However that still won't solve the underlying problem in uvloop, only reduce the chance it will happen. |
I need to set None in happy_eyeballs_delay to disable "Happy Eyeballs" right? |
Yes |
Describe the bug
In our service we had aiohttp==3.8.5 and upgraded aiohttp to 3.10.5 version. That is all. In production now we have issues like issue below.
Maybe i should to write issue to another libs, tell me about it if so, or maybe you have your own fix then tell me aiohttp version i need to upgrade in my service.
To Reproduce
Unfortunetly we have it only in production mode, i do not know how reproduce it in stage mode.
Expected behavior
No issues like issue above.
Logs/tracebacks
Python Version
aiohttp Version
multidict Version
propcache Version
yarl Version
OS
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
Related component
Server, Client
Additional context
aiohttp==3.10.5
aiohttp_traversal==0.11.0
aiojobs==1.2.0
asyncpg==0.29.0
orjson==3.9.10
uvloop==0.19.0
yarl==1.12.1
Code of Conduct
The text was updated successfully, but these errors were encountered: