Update dependency aiohttp to ~=3.10.2 #67
No reviewers
Labels
No Label
Kind/Breaking
Kind/Bug
Kind/Documentation
Kind/Enhancement
Kind/Feature
Kind/Security
Kind/Testing
Priority
Critical
Priority
High
Priority
Low
Priority
Medium
Reviewed
Confirmed
Reviewed
Duplicate
Reviewed
Invalid
Reviewed
Won't Fix
Status
Abandoned
Status
Blocked
Status
Need More Info
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: GarbageReminder/TelegramBot#67
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "renovate/aiohttp-3.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
~=3.9.5
->~=3.10.2
Release Notes
aio-libs/aiohttp (aiohttp)
v3.10.2
Compare Source
===================
Bug fixes
Fixed server checks for circular symbolic links to be compatible with Python 3.13 -- by :user:
steverep
.Related issues and pull requests on GitHub:
:issue:
8565
.Fixed request body not being read when ignoring an Upgrade request -- by :user:
Dreamsorcerer
.Related issues and pull requests on GitHub:
:issue:
8597
.Fixed an edge case where shutdown would wait for timeout when the handler was already completed -- by :user:
Dreamsorcerer
.Related issues and pull requests on GitHub:
:issue:
8611
.Fixed connecting to
npipe://
,tcp://
, andunix://
urls -- by :user:bdraco
.Related issues and pull requests on GitHub:
:issue:
8632
.Fixed WebSocket ping tasks being prematurely garbage collected -- by :user:
bdraco
.There was a small risk that WebSocket ping tasks would be prematurely garbage collected because the event loop only holds a weak reference to the task. The garbage collection risk has been fixed by holding a strong reference to the task. Additionally, the task is now scheduled eagerly with Python 3.12+ to increase the chance it can be completed immediately and avoid having to hold any references to the task.
Related issues and pull requests on GitHub:
:issue:
8641
.Fixed incorrectly following symlinks for compressed file variants -- by :user:
steverep
.Related issues and pull requests on GitHub:
:issue:
8652
.Removals and backward incompatible breaking changes
Removed
Request.wait_for_disconnection()
, which was mistakenly added briefly in 3.10.0 -- by :user:Dreamsorcerer
.Related issues and pull requests on GitHub:
:issue:
8636
.Contributor-facing changes
Fixed monkey patches for
Path.stat()
andPath.is_dir()
for Python 3.13 compatibility -- by :user:steverep
.Related issues and pull requests on GitHub:
:issue:
8551
.Miscellaneous internal changes
Improved WebSocket performance when messages are sent or received frequently -- by :user:
bdraco
.The WebSocket heartbeat scheduling algorithm was improved to reduce the
asyncio
scheduling overhead by decreasing the number ofasyncio.TimerHandle
creations and cancellations.Related issues and pull requests on GitHub:
:issue:
8608
.Minor improvements to various type annotations -- by :user:
Dreamsorcerer
.Related issues and pull requests on GitHub:
:issue:
8634
.v3.10.1
Compare Source
========================
Bug fixes
Fixed WebSocket server heartbeat timeout logic to terminate :py:meth:
~aiohttp.ClientWebSocketResponse.receive
and return :py:class:~aiohttp.ServerTimeoutError
-- by :user:arcivanov
.When a WebSocket pong message was not received, the :py:meth:
~aiohttp.ClientWebSocketResponse.receive
operation did not terminate. This change causes_pong_not_received
to feed thereader
an error message, causing pending :py:meth:~aiohttp.ClientWebSocketResponse.receive
to terminate and return the error message. The error message contains the exception :py:class:~aiohttp.ServerTimeoutError
.Related issues and pull requests on GitHub:
:issue:
8540
.Fixed url dispatcher index not matching when a variable is preceded by a fixed string after a slash -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
8566
.Removals and backward incompatible breaking changes
Creating :py:class:
aiohttp.TCPConnector
, :py:class:aiohttp.ClientSession
, :py:class:~aiohttp.resolver.ThreadedResolver
:py:class:aiohttp.web.Server
, or :py:class:aiohttp.CookieJar
instances without a running event loop now raises a :exc:RuntimeError
-- by :user:asvetlov
.Creating these objects without a running event loop was deprecated in :issue:
3372
which was released in version 3.5.0.This change first appeared in version 3.10.0 as :issue:
6378
.Related issues and pull requests on GitHub:
:issue:
8555
, :issue:8583
.v3.10.0
Compare Source
========================
Bug fixes
Fixed server response headers for
Content-Type
andContent-Encoding
forstatic compressed files -- by :user:
steverep
.Server will now respond with a
Content-Type
appropriate for the compressedfile (e.g.
"application/gzip"
), and omit theContent-Encoding
header.Users should expect that most clients will no longer decompress such responses
by default.
Related issues and pull requests on GitHub:
:issue:
4462
.Fixed duplicate cookie expiration calls in the CookieJar implementation
Related issues and pull requests on GitHub:
:issue:
7784
.Adjusted
FileResponse
to check file existence and access when preparing the response -- by :user:steverep
.The :py:class:
~aiohttp.web.FileResponse
class was modified to respond with403 Forbidden or 404 Not Found as appropriate. Previously, it would cause a
server error if the path did not exist or could not be accessed. Checks for
existence, non-regular files, and permissions were expected to be done in the
route handler. For static routes, this now permits a compressed file to exist
without its uncompressed variant and still be served. In addition, this
changes the response status for files without read permission to 403, and for
non-regular files from 404 to 403 for consistency.
Related issues and pull requests on GitHub:
:issue:
8182
.Fixed
AsyncResolver
to matchThreadedResolver
behavior-- by :user:
bdraco
.On system with IPv6 support, the :py:class:
~aiohttp.resolver.AsyncResolver
would not fallbackto providing A records when AAAA records were not available.
Additionally, unlike the :py:class:
~aiohttp.resolver.ThreadedResolver
, the :py:class:~aiohttp.resolver.AsyncResolver
did not handle link-local addresses correctly.
This change makes the behavior consistent with the :py:class:
~aiohttp.resolver.ThreadedResolver
.Related issues and pull requests on GitHub:
:issue:
8270
.Fixed
ws_connect
not respectingreceive_timeout`` on WS(S) connection. -- by :user:
arcivanov`.Related issues and pull requests on GitHub:
:issue:
8444
.Removed blocking I/O in the event loop for static resources and refactored
exception handling -- by :user:
steverep
.File system calls when handling requests for static routes were moved to a
separate thread to potentially improve performance. Exception handling
was tightened in order to only return 403 Forbidden or 404 Not Found responses
for expected scenarios; 500 Internal Server Error would be returned for any
unknown errors.
Related issues and pull requests on GitHub:
:issue:
8507
.Features
Added a Request.wait_for_disconnection() method, as means of allowing request handlers to be notified of premature client disconnections.
Related issues and pull requests on GitHub:
:issue:
2492
.Added 5 new exceptions: :py:exc:
~aiohttp.InvalidUrlClientError
, :py:exc:~aiohttp.RedirectClientError
,:py:exc:
~aiohttp.NonHttpUrlClientError
, :py:exc:~aiohttp.InvalidUrlRedirectClientError
,:py:exc:
~aiohttp.NonHttpUrlRedirectClientError
:py:exc:
~aiohttp.InvalidUrlRedirectClientError
, :py:exc:~aiohttp.NonHttpUrlRedirectClientError
are raised instead of :py:exc:
ValueError
or :py:exc:~aiohttp.InvalidURL
when the redirect URL is invalid. Classes:py:exc:
~aiohttp.InvalidUrlClientError
, :py:exc:~aiohttp.RedirectClientError
,:py:exc:
~aiohttp.NonHttpUrlClientError
are base for them.The :py:exc:
~aiohttp.InvalidURL
now exposes adescription
property with the text explanation of the error details.-- by :user:
setla
, :user:AraHaan
, and :user:bdraco
Related issues and pull requests on GitHub:
:issue:
2507
, :issue:3315
, :issue:6722
, :issue:8481
, :issue:8482
.Added a feature to retry closed connections automatically for idempotent methods. -- by :user:
Dreamsorcerer
Related issues and pull requests on GitHub:
:issue:
7297
.Implemented filter_cookies() with domain-matching and path-matching on the keys, instead of testing every single cookie.
This may break existing cookies that have been saved with
CookieJar.save()
. Cookies can be migrated with this script::Related issues and pull requests on GitHub:
:issue:
7583
, :issue:8535
.Separated connection and socket timeout errors, from ServerTimeoutError.
Related issues and pull requests on GitHub:
:issue:
7801
.Implemented happy eyeballs
Related issues and pull requests on GitHub:
:issue:
7954
.Added server capability to check for static files with Brotli compression via a
.br
extension -- by :user:steverep
.Related issues and pull requests on GitHub:
:issue:
8062
.Removals and backward incompatible breaking changes
The shutdown logic in 3.9 waited on all tasks, which caused issues with some libraries.
In 3.10 we've changed this logic to only wait on request handlers. This means that it's
important for developers to correctly handle the lifecycle of background tasks using a
library such as
aiojobs
. If an application is usinghandler_cancellation=True
thenit is also a good idea to ensure that any :func:
asyncio.shield
calls are replaced with:func:
aiojobs.aiohttp.shield
.Please read the updated documentation on these points:
https://docs.aiohttp.org/en/stable/web_advanced.html#graceful-shutdown
https://docs.aiohttp.org/en/stable/web_advanced.html#web-handler-cancellation
-- by :user:
Dreamsorcerer
Related issues and pull requests on GitHub:
:issue:
8495
.Improved documentation
Added documentation for
aiohttp.web.FileResponse
.Related issues and pull requests on GitHub:
:issue:
3958
.Improved the docs for the
ssl
params.Related issues and pull requests on GitHub:
:issue:
8403
.Contributor-facing changes
Enabled HTTP parser tests originally intended for 3.9.2 release -- by :user:
pajod
.Related issues and pull requests on GitHub:
:issue:
8088
.Miscellaneous internal changes
Improved URL handler resolution time by indexing resources in the UrlDispatcher.
For applications with a large number of handlers, this should increase performance significantly.
-- by :user:
bdraco
Related issues and pull requests on GitHub:
:issue:
7829
.Added
nacl_middleware <https://github.com/CosmicDNA/nacl_middleware>
_ to the list of middlewares in the third party section of the documentation.Related issues and pull requests on GitHub:
:issue:
8346
.Minor improvements to static typing -- by :user:
Dreamsorcerer
.Related issues and pull requests on GitHub:
:issue:
8364
.Added a 3.11-specific overloads to
ClientSession
-- by :user:max-muoto
.Related issues and pull requests on GitHub:
:issue:
8463
.Simplified path checks for
UrlDispatcher.add_static()
method -- by :user:steverep
.Related issues and pull requests on GitHub:
:issue:
8491
.Avoided creating a future on every websocket receive -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
8498
.Updated identity checks for all
WSMsgType
type compares -- by :user:bdraco
.Related issues and pull requests on GitHub:
:issue:
8501
.When using Python 3.12 or later, the writer is no longer scheduled on the event loop if it can finish synchronously. Avoiding event loop scheduling reduces latency and improves performance. -- by :user:
bdraco
.Related issues and pull requests on GitHub:
:issue:
8510
.Restored :py:class:
~aiohttp.resolver.AsyncResolver
to be the default resolver. -- by :user:bdraco
.:py:class:
~aiohttp.resolver.AsyncResolver
was disabled by default becauseof IPv6 compatibility issues. These issues have been resolved and
:py:class:
~aiohttp.resolver.AsyncResolver
is again now the default resolver.Related issues and pull requests on GitHub:
:issue:
8522
.Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update (~=3.10.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the
ignoreDeps
array of your Renovate config.If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.