-
-
Notifications
You must be signed in to change notification settings - Fork 183
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
"unclosed transport" warning with long running client under Python 3.10 #1211
Comments
interesting, why only python3.10, here's the trace with
|
this seems to be a bug with python3.10 and/or aiohttp. Even if I explicitly release the connections python3.10 still complains. Note that aiohttp will release the connection back to the pool at the end of the stream (As in this case) so aiobotocore does not need to explicitly release it. In this case I don't think there's a "leak" because the connection is still re-usable as the body was fully read. I suggest upgrading to 3.11 or asking aiohttp why this is the case in 3.10 |
Describe the bug
Running Python 3.10, making any call to S3 without immediately closing the S3 client will cause the following warning to be emitted.
Here is a minimally reproducible example:
Running this outputs the following:
Commenting out the first sleep, the warning disappears:
Checklist
pip check
passes without errorspip freeze
resultspip freeze results
Environment:
Additional context
botocore
and the issue doesn't occur. Though the code isn't exactly equivalent since clients are not context managers inbotocore
aiohttp
and the issue doesn't occur either.aiobotocore==1.4.0
andaiohttp==3.7.0
. Any earlier versions and I start to see other errors that prevents the code from running.The text was updated successfully, but these errors were encountered: