-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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
Bump to aiohttp 3.8.0 #58974
Bump to aiohttp 3.8.0 #58974
Conversation
Upgraded a few production installs and everything seems ok. There are likely going to be side effects that are unseen so good to get it in at the top of the release cycle |
@@ -0,0 +1,67 @@ | |||
"""Provide backwards compat for async_timeout.""" |
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.
maybe more fit for living inside utils?
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.
I tried to mirror how block_async_io works with the thought it would be easy to delete the file once the time window had passed.
I can move it if utils is a better place.
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.
I think it's fine here. It will be removed anyway.
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.
Let's verify it works with ingress and then this is good to go 👍
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.
Looks Ok for Axis, deCONZ and UniFi
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.
LG for nest
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.
Tested a handful of add-ons with ingress and no apparent issue was shown while using them 👍
Thanks for testing. Let's merge this so devs have the most amount of warning possible to update deps that need to have the |
Discovered |
Breaking change
Bump to
aiohttp
to 3.8.0This version of
aiohttp
requiresasync_timeout
4.0.0 which has multiple breaking changes:async_timeout.timeout
drops theloop=
keyword arg.async_timeout.current_task
has been removed.timeout.remaining
property has been removed. (No backward compatibility is provided as all instances in core have been changed)timeout.timeout
property has been removed. (No backward compatibility is provided as no usage of this was found)To facilitate the transition, temporary compatibility code has been added. The backwards compatibility will be removed in 2022.2:
async_timeout.timeout
is replaced with a backwards compatible transitional version that logs a warning when callers use theloop=
argument.async_timeout.current_task
is replaced with a backwards compatible transitional version that warnsasyncio.current_task
should be used instead.Changes: https://github.com/aio-libs/aiohttp/releases/tag/v3.8.0 https://github.com/aio-libs/async-timeout/releases/tag/v4.0.0
Type of change
Additional information
Checklist
black --fast homeassistant tests
)If user exposed functionality or configuration variables are added/changed:
If the code communicates with devices, web services, or third-party tools:
Updated and included derived files by running:
python3 -m script.hassfest
.requirements_all.txt
.Updated by running
python3 -m script.gen_requirements_all
..coveragerc
.The integration reached or maintains the following Integration Quality Scale:
To help with the load of incoming pull requests: