Skip to content
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

Redesign shutdown process #7718

Merged
merged 21 commits into from
Nov 2, 2023
Merged

Redesign shutdown process #7718

merged 21 commits into from
Nov 2, 2023

Conversation

Dreamsorcerer
Copy link
Member

@Dreamsorcerer Dreamsorcerer commented Oct 17, 2023

This contains a few changes to rework the shutdown process to be a bit clearer and better match user expectations.

To summarise, I'm proposing the shutdown process should look like this now:

  1. Stop each site listening for new connections.
  2. Close idle keep-alive connections (and set active ones to close upon completion).
  3. Call on_shutdown signal (should be used to close websocket connections).
  4. Wait for running tasks to complete (with timeout).
  5. Close any remaining connections (with timeout again).
  6. Call on_cleanup signal.
  7. Cancel any remaining tasks and wait on them.

Docs demo preview: https://aiohttp--7718.org.readthedocs.build/en/7718/web_advanced.html#graceful-shutdown

tests/test_run_app.py Fixed Show fixed Hide fixed
tests/test_run_app.py Fixed Show fixed Hide fixed
@Dreamsorcerer Dreamsorcerer mentioned this pull request Oct 19, 2023
8 tasks
tests/test_run_app.py Dismissed Show dismissed Hide dismissed
tests/test_run_app.py Dismissed Show dismissed Hide dismissed
@psf-chronographer psf-chronographer bot added the bot:chronographer:provided There is a change note present in this PR label Oct 23, 2023
@Dreamsorcerer Dreamsorcerer marked this pull request as ready for review October 23, 2023 20:59
docs/web_advanced.rst Outdated Show resolved Hide resolved
@webknjaz
Copy link
Member

Cancel any remaining tasks and wait on them.

Does this pose a deadlock threat?

@Dreamsorcerer
Copy link
Member Author

Cancel any remaining tasks and wait on them.

Does this pose a deadlock threat?

I think there is the possibility that a task could stop the program exiting, but at that point the rest of shutdown has already happened, so it'll be as safe as it can be for someone to kill the program. This step is unchanged from the 3.8 release.

@Dreamsorcerer
Copy link
Member Author

Cancel any remaining tasks and wait on them.

Does this pose a deadlock threat?

I think there is the possibility that a task could stop the program exiting, but at that point the rest of shutdown has already happened, so it'll be as safe as it can be for someone to kill the program. This step is unchanged from the 3.8 release.

In fact, I just remembered that this code is copied from asyncio.run(), so it'll be consistent with asyncio generally.

Co-authored-by: Sviatoslav Sydorenko <sviat@redhat.com>
@codecov
Copy link

codecov bot commented Oct 27, 2023

Codecov Report

Merging #7718 (4d21a28) into master (d8936aa) will increase coverage by 0.02%.
Report is 5 commits behind head on master.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #7718      +/-   ##
==========================================
+ Coverage   97.36%   97.38%   +0.02%     
==========================================
  Files         106      106              
  Lines       31718    31798      +80     
  Branches     3633     3645      +12     
==========================================
+ Hits        30881    30967      +86     
+ Misses        633      627       -6     
  Partials      204      204              
Flag Coverage Δ
CI-GHA 97.30% <97.93%> (+0.01%) ⬆️
OS-Linux 96.97% <96.90%> (+0.02%) ⬆️
OS-Windows 95.44% <95.87%> (+0.02%) ⬆️
OS-macOS 96.64% <96.90%> (+0.03%) ⬆️
Py-3.10.11 95.37% <93.81%> (+0.01%) ⬆️
Py-3.10.13 96.82% <94.84%> (+0.01%) ⬆️
Py-3.11.6 96.48% <90.72%> (+<0.01%) ⬆️
Py-3.8.10 95.33% <93.81%> (+0.01%) ⬆️
Py-3.8.18 96.75% <94.84%> (+0.01%) ⬆️
Py-3.9.13 95.33% <95.87%> (+0.02%) ⬆️
Py-3.9.18 96.79% <96.90%> (+0.03%) ⬆️
Py-pypy7.3.11 96.19% <94.84%> (+0.01%) ⬆️
VM-macos 96.64% <96.90%> (+0.03%) ⬆️
VM-ubuntu 96.97% <96.90%> (+0.02%) ⬆️
VM-windows 95.44% <95.87%> (+0.02%) ⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files Coverage Δ
aiohttp/web.py 99.27% <100.00%> (+0.11%) ⬆️
aiohttp/web_runner.py 97.75% <100.00%> (-0.08%) ⬇️
aiohttp/web_server.py 95.34% <100.00%> (+0.34%) ⬆️
aiohttp/worker.py 91.86% <ø> (ø)
tests/test_run_app.py 98.46% <100.00%> (+0.20%) ⬆️
tests/test_worker.py 98.95% <100.00%> (+0.01%) ⬆️

... and 5 files with indirect coverage changes

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@Dreamsorcerer
Copy link
Member Author

I'm merging this, if there's any feedback, I can update it before the final release (maybe in a week or so).

@Dreamsorcerer Dreamsorcerer merged commit 107dd24 into master Nov 2, 2023
29 of 34 checks passed
@Dreamsorcerer Dreamsorcerer deleted the rework-shutdown branch November 2, 2023 22:47
Copy link
Contributor

patchback bot commented Nov 2, 2023

Backport to 3.9: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 107dd24 on top of patchback/backports/3.9/107dd2445720cf354c84c3a271691f14e2e2875e/pr-7718

Backporting merged PR #7718 into master

  1. Ensure you have a local repo clone of your fork. Unless you cloned it
    from the upstream, this would be your origin remote.
  2. Make sure you have an upstream repo added as a remote too. In these
    instructions you'll refer to it by the name upstream. If you don't
    have it, here's how you can add it:
    $ git remote add upstream https://github.com/aio-libs/aiohttp.git
  3. Ensure you have the latest copy of upstream and prepare a branch
    that will hold the backported code:
    $ git fetch upstream
    $ git checkout -b patchback/backports/3.9/107dd2445720cf354c84c3a271691f14e2e2875e/pr-7718 upstream/3.9
  4. Now, cherry-pick PR Redesign shutdown process #7718 contents into that branch:
    $ git cherry-pick -x 107dd2445720cf354c84c3a271691f14e2e2875e
    If it'll yell at you with something like fatal: Commit 107dd2445720cf354c84c3a271691f14e2e2875e is a merge but no -m option was given., add -m 1 as follows instead:
    $ git cherry-pick -m1 -x 107dd2445720cf354c84c3a271691f14e2e2875e
  5. At this point, you'll probably encounter some merge conflicts. You must
    resolve them in to preserve the patch from PR Redesign shutdown process #7718 as close to the
    original as possible.
  6. Push this branch to your fork on GitHub:
    $ git push origin patchback/backports/3.9/107dd2445720cf354c84c3a271691f14e2e2875e/pr-7718
  7. Create a PR, ensure that the CI is green. If it's not — update it so that
    the tests and any other checks pass. This is it!
    Now relax and wait for the maintainers to process your pull request
    when they have some cycles to do reviews. Don't worry — they'll tell you if
    any improvements are necessary when the time comes!

🤖 @patchback
I'm built with octomachinery and
my source is open — https://github.com/sanitizers/patchback-github-app.

Dreamsorcerer added a commit that referenced this pull request Nov 2, 2023
This contains a few changes to rework the shutdown process to be a bit
clearer and better match user expectations.

To summarise, I'm proposing the shutdown process should look like this
now:

1. Stop each site listening for new connections.
2. Close idle keep-alive connections (and set active ones to close upon
completion).
3. Call on_shutdown signal (should be used to close websocket
connections).
4. Wait for running tasks to complete (with timeout).
5. Close any remaining connections (with timeout again).
6. Call on_cleanup signal.
7. Cancel any remaining tasks and wait on them.

Docs demo preview:
https://aiohttp--7718.org.readthedocs.build/en/7718/web_advanced.html#graceful-shutdown

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: Sviatoslav Sydorenko <sviat@redhat.com>
(cherry picked from commit 107dd24)
@bdraco
Copy link
Member

bdraco commented Nov 2, 2023

I'm merging this, if there's any feedback, I can update it before the final release (maybe in a week or so).

Sorry for the late feedback, I wasn't shut if this was ready to test or not.

I tested this with Home Assistant, and shutdown is delayed if we don't patch out wait.

Home Assistant has long running tasks that are created after aiohttp starts up, and are expected to be torn down after aiohttp is shutdown. Unfortunately we can't change that design to shutdown aiohttp later.

Patching out wait it probably fine for Home Assistant. It might be nice to have a way to disable the shutdown logic a bit more cleanly though.

@@ -0,0 +1,3 @@
Fixed keep-alive connections stopping a graceful shutdown.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Dreamsorcerer “fixed” implies a “bugfix” changelog note type, but the filename says “feature”. If it's both, it might be worth splitting into two fragments.

@webknjaz
Copy link
Member

webknjaz commented Nov 2, 2023

Home Assistant has long running tasks that are created after aiohttp starts up, and are expected to be torn down after aiohttp is shutdown. Unfortunately we can't change that design to shutdown aiohttp later.

Maybe, you could shield them from being cancelled, doing an unshielded cancellation later, manually?

@webknjaz
Copy link
Member

webknjaz commented Nov 3, 2023

Home Assistant has long running tasks that are created after aiohttp starts up, and are expected to be torn down after aiohttp is shutdown. Unfortunately we can't change that design to shutdown aiohttp later.

What if there was an interface to augment the new starting_tasks structure with your tasks? As I understand, you track what's yours, right?

@webknjaz
Copy link
Member

webknjaz commented Nov 3, 2023

@Dreamsorcerer I'm not very familiar with the shutdown internals, so I can't contribute an involved feedback. Just want to say that I don't see anything obviously wrong, and it seems like a good idea.

@webknjaz
Copy link
Member

webknjaz commented Nov 3, 2023

Unfortunately we can't change that design to shutdown aiohttp later.

@bdraco could you explain why?

@bdraco
Copy link
Member

bdraco commented Nov 3, 2023

Unfortunately we can't change that design to shutdown aiohttp later.

@bdraco could you explain why?

Home Assistant has its own tasks that are created with our helper that we can track, but there are also ~1600 dependencies that can start their own tasks so we don't have a direct way to manage them.

While most of them will listen for a stop event and cancel the tasks, there are many custom integrations (and libraries) that don't and we can't wait for them to shutdown because we would end up waiting forever in many cases.

To give some better context, there are likely quite a few integrations that have a task running a retry loop when a device is offline that keep trying to reconnect forever until Home Assistant shuts down the event loop from under them.

@webknjaz
Copy link
Member

webknjaz commented Nov 3, 2023

@bdraco have you tried exploring having a separate event loop for those?

@Dreamsorcerer
Copy link
Member Author

@bdraco We already discussed this in the testing issue. My understanding is that HA is using the runners directly, so in this PR I've moved the wait logic into run_app(). This means it should have no impact on HA anymore, and there isn't anything there to patch out. For users using run_app(), this is the entry point of the event loop and we expect to control the lifecycle of the event loop.

@Dreamsorcerer
Copy link
Member Author

Dreamsorcerer commented Nov 3, 2023

(This is also now highlighted in the docs section linked at the top of the PR)

@bdraco
Copy link
Member

bdraco commented Nov 3, 2023

@bdraco We already discussed this in the testing issue. My understanding is that HA is using the runners directly, so in this PR I've moved the wait logic into run_app(). This means it should have no impact on HA anymore, and there isn't anything there to patch out. For users using run_app(), this is the entry point of the event loop and we expect to control the lifecycle of the event loop.

I agree that I shouldn't be seeing a problem anymore, but I can reproduce still. I will double check that I haven't screwed something up with my testing.

@bdraco
Copy link
Member

bdraco commented Nov 3, 2023

TLDR: This PR solves the issue, there is an unrelated regression on my Home Assistant integration branch from trying to test too many changes at once that resulted in a bad test.

The problem goes away when I use Home Assistant stable + this PR. I must have a regression my Home Assistant integration branch that is blocking shutdown. I will bisect and find the bad commit but its certainly unrelated.

I didn't notice since I was running 3.9 prior to this PR which was always shutting down slowly (I didn't want to forget to make sure this was sorted) since it wasn't patched and I assumed the slow shutdown was still from that.

Thanks for getting this sorted. Sorry about the bad test.

@bdraco
Copy link
Member

bdraco commented Nov 3, 2023

I found the bad commit, its definitely unrelated. Sorry again for the side trip. The good news is that 3.9 is working well in production 👍

renovate bot referenced this pull request in allenporter/pyrainbird Nov 20, 2023
[![Mend Renovate logo
banner](https://app.renovatebot.com/images/banner.svg)](https://renovatebot.com)

This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence |
|---|---|---|---|---|---|
| [aiohttp](https://togithub.com/aio-libs/aiohttp) | `==3.8.6` ->
`==3.9.0` |
[![age](https://developer.mend.io/api/mc/badges/age/pypi/aiohttp/3.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![adoption](https://developer.mend.io/api/mc/badges/adoption/pypi/aiohttp/3.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![passing](https://developer.mend.io/api/mc/badges/compatibility/pypi/aiohttp/3.8.6/3.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|
[![confidence](https://developer.mend.io/api/mc/badges/confidence/pypi/aiohttp/3.8.6/3.9.0?slim=true)](https://docs.renovatebot.com/merge-confidence/)
|

---

### Release Notes

<details>
<summary>aio-libs/aiohttp (aiohttp)</summary>

###
[`v3.9.0`](https://togithub.com/aio-libs/aiohttp/blob/HEAD/CHANGES.rst#390-2023-11-18)

[Compare
Source](https://togithub.com/aio-libs/aiohttp/compare/v3.8.6...v3.9.0)

\==================

## Features

- Introduced `AppKey` for static typing support of `Application`
storage.
See
https://docs.aiohttp.org/en/stable/web_advanced.html#application-s-config

    `#&#8203;5864 <https://github.com/aio-libs/aiohttp/issues/5864>`\_

- Added a graceful shutdown period which allows pending tasks to
complete before the application's cleanup is called.
The period can be adjusted with the `shutdown_timeout` parameter. -- by
:user:`Dreamsorcerer`.
See
https://docs.aiohttp.org/en/latest/web_advanced.html#graceful-shutdown

    `#&#8203;7188 <https://github.com/aio-libs/aiohttp/issues/7188>`\_

- Added `handler_cancellation
<https://docs.aiohttp.org/en/stable/web_advanced.html#web-handler-cancellation>`\_
parameter to cancel web handler on client disconnection. -- by
:user:`mosquito`
This (optionally) reintroduces a feature removed in a previous release.
Recommended for those looking for an extra level of protection against
denial-of-service attacks.

    `#&#8203;7056 <https://github.com/aio-libs/aiohttp/issues/7056>`\_

- Added support for setting response header parameters `max_line_size`
and `max_field_size`.

    `#&#8203;2304 <https://github.com/aio-libs/aiohttp/issues/2304>`\_

- Added `auto_decompress` parameter to `ClientSession.request` to
override `ClientSession._auto_decompress`. -- by :user:`Daste745`

    `#&#8203;3751 <https://github.com/aio-libs/aiohttp/issues/3751>`\_

-   Changed `raise_for_status` to allow a coroutine.

    `#&#8203;3892 <https://github.com/aio-libs/aiohttp/issues/3892>`\_

- Added client brotli compression support (optional with runtime check).

    `#&#8203;5219 <https://github.com/aio-libs/aiohttp/issues/5219>`\_

- Added `client_max_size` to `BaseRequest.clone()` to allow overriding
the request body size. -- :user:`anesabml`.

    `#&#8203;5704 <https://github.com/aio-libs/aiohttp/issues/5704>`\_

-   Added a middleware type alias `aiohttp.typedefs.Middleware`.

    `#&#8203;5898 <https://github.com/aio-libs/aiohttp/issues/5898>`\_

- Exported `HTTPMove` which can be used to catch any redirection request
    that has a location -- :user:`dreamsorcerer`.

    `#&#8203;6594 <https://github.com/aio-libs/aiohttp/issues/6594>`\_

- Changed the `path` parameter in `web.run_app()` to accept a
`pathlib.Path` object.

    `#&#8203;6839 <https://github.com/aio-libs/aiohttp/issues/6839>`\_

- Performance: Skipped filtering `CookieJar` when the jar is empty or
all cookies have expired.

    `#&#8203;7819 <https://github.com/aio-libs/aiohttp/issues/7819>`\_

- Performance: Only check origin if insecure scheme and there are
origins to treat as secure, in `CookieJar.filter_cookies()`.

    `#&#8203;7821 <https://github.com/aio-libs/aiohttp/issues/7821>`\_

- Performance: Used timestamp instead of `datetime` to achieve faster
cookie expiration in `CookieJar`.

    `#&#8203;7824 <https://github.com/aio-libs/aiohttp/issues/7824>`\_

- Added support for passing a custom server name parameter to HTTPS
connection.

    `#&#8203;7114 <https://github.com/aio-libs/aiohttp/issues/7114>`\_

- Added support for using Basic Auth credentials from :file:`.netrc`
file when making HTTP requests with the
:py:class:`~aiohttp.ClientSession` `trust_env` argument is set to
`True`. -- by :user:`yuvipanda`.

    `#&#8203;7131 <https://github.com/aio-libs/aiohttp/issues/7131>`\_

-   Turned access log into no-op when the logger is disabled.

    `#&#8203;7240 <https://github.com/aio-libs/aiohttp/issues/7240>`\_

- Added typing information to `RawResponseMessage`. -- by
:user:`Gobot1234`

    `#&#8203;7365 <https://github.com/aio-libs/aiohttp/issues/7365>`\_

- Removed `async-timeout` for Python 3.11+ (replaced with
`asyncio.timeout()` on newer releases).

    `#&#8203;7502 <https://github.com/aio-libs/aiohttp/issues/7502>`\_

- Added support for `brotlicffi` as an alternative to `brotli` (fixing
Brotli support on PyPy).

    `#&#8203;7611 <https://github.com/aio-libs/aiohttp/issues/7611>`\_

- Added `WebSocketResponse.get_extra_info()` to access a protocol
transport's extra info.

    `#&#8203;7078 <https://github.com/aio-libs/aiohttp/issues/7078>`\_

-   Allow `link` argument to be set to None/empty in HTTP 451 exception.

    `#&#8203;7689 <https://github.com/aio-libs/aiohttp/issues/7689>`\_

## Bugfixes

- Implemented stripping the trailing dots from fully-qualified domain
names in `Host` headers and TLS context when acting as an HTTP client.
This allows the client to connect to URLs with FQDN host name like
`https://example.com./`.
    \-- by :user:`martin-sucha`.

    `#&#8203;3636 <https://github.com/aio-libs/aiohttp/issues/3636>`\_

- Fixed client timeout not working when incoming data is always
available without waiting. -- by :user:`Dreamsorcerer`.

    `#&#8203;5854 <https://github.com/aio-libs/aiohttp/issues/5854>`\_

- Fixed `readuntil` to work with a delimiter of more than one character.

    `#&#8203;6701 <https://github.com/aio-libs/aiohttp/issues/6701>`\_

-   Added `__repr__` to `EmptyStreamReader` to avoid `AttributeError`.

    `#&#8203;6916 <https://github.com/aio-libs/aiohttp/issues/6916>`\_

-   Fixed bug when using `TCPConnector` with `ttl_dns_cache=0`.

    `#&#8203;7014 <https://github.com/aio-libs/aiohttp/issues/7014>`\_

- Fixed response returned from expect handler being thrown away. -- by
:user:`Dreamsorcerer`

    `#&#8203;7025 <https://github.com/aio-libs/aiohttp/issues/7025>`\_

- Avoided raising `UnicodeDecodeError` in multipart and in HTTP headers
parsing.

    `#&#8203;7044 <https://github.com/aio-libs/aiohttp/issues/7044>`\_

- Changed `sock_read` timeout to start after writing has finished,
avoiding read timeouts caused by an unfinished write. -- by
:user:`dtrifiro`

    `#&#8203;7149 <https://github.com/aio-libs/aiohttp/issues/7149>`\_

-   Fixed missing query in tracing method URLs when using `yarl` 1.9+.

    `#&#8203;7259 <https://github.com/aio-libs/aiohttp/issues/7259>`\_

- Changed max 32-bit timestamp to an aware datetime object, for
consistency with the non-32-bit one, and to avoid a `DeprecationWarning`
on Python 3.12.

    `#&#8203;7302 <https://github.com/aio-libs/aiohttp/issues/7302>`\_

- Fixed `EmptyStreamReader.iter_chunks()` never ending. -- by
:user:`mind1m`

    `#&#8203;7616 <https://github.com/aio-libs/aiohttp/issues/7616>`\_

- Fixed a rare `RuntimeError: await wasn't used with future` exception.
-- by :user:`stalkerg`

    `#&#8203;7785 <https://github.com/aio-libs/aiohttp/issues/7785>`\_

-   Fixed issue with insufficient HTTP method and version validation.

    `#&#8203;7700 <https://github.com/aio-libs/aiohttp/issues/7700>`\_

-   Added check to validate that absolute URIs have schemes.

    `#&#8203;7712 <https://github.com/aio-libs/aiohttp/issues/7712>`\_

- Fixed unhandled exception when Python HTTP parser encounters unpaired
Unicode surrogates.

    `#&#8203;7715 <https://github.com/aio-libs/aiohttp/issues/7715>`\_

- Updated parser to disallow invalid characters in header field names
and stop accepting LF as a request line separator.

    `#&#8203;7719 <https://github.com/aio-libs/aiohttp/issues/7719>`\_

-   Fixed Python HTTP parser not treating 204/304/1xx as an empty body.

    `#&#8203;7755 <https://github.com/aio-libs/aiohttp/issues/7755>`\_

-   Ensure empty body response for 1xx/204/304 per RFC 9112 sec 6.3.

    `#&#8203;7756 <https://github.com/aio-libs/aiohttp/issues/7756>`\_

- Fixed an issue when a client request is closed before completing a
chunked payload. -- by :user:`Dreamsorcerer`

    `#&#8203;7764 <https://github.com/aio-libs/aiohttp/issues/7764>`\_

-   Edge Case Handling for ResponseParser for missing reason value.

    `#&#8203;7776 <https://github.com/aio-libs/aiohttp/issues/7776>`\_

- Fixed `ClientWebSocketResponse.close_code` being erroneously set to
`None` when there are concurrent async tasks receiving data and closing
the connection.

    `#&#8203;7306 <https://github.com/aio-libs/aiohttp/issues/7306>`\_

-   Added HTTP method validation.

    `#&#8203;6533 <https://github.com/aio-libs/aiohttp/issues/6533>`\_

- Fixed arbitrary sequence types being allowed to inject values via
version parameter. -- by :user:`Dreamsorcerer`

    `#&#8203;7835 <https://github.com/aio-libs/aiohttp/issues/7835>`\_

- Performance: Fixed increase in latency with small messages from
websocket compression changes.

    `#&#8203;7797 <https://github.com/aio-libs/aiohttp/issues/7797>`\_

## Improved Documentation

- Fixed the `ClientResponse.release`'s type in the doc. Changed from
`comethod` to `method`.

    `#&#8203;5836 <https://github.com/aio-libs/aiohttp/issues/5836>`\_

- Added information on behavior of base_url parameter in
`ClientSession`.

    `#&#8203;6647 <https://github.com/aio-libs/aiohttp/issues/6647>`\_

-   Fixed `ClientResponseError` docs.

    `#&#8203;6700 <https://github.com/aio-libs/aiohttp/issues/6700>`\_

-   Updated Redis code examples to follow the latest API.

    `#&#8203;6907 <https://github.com/aio-libs/aiohttp/issues/6907>`\_

- Added a note about possibly needing to update headers when using
`on_response_prepare`. -- by :user:`Dreamsorcerer`

    `#&#8203;7283 <https://github.com/aio-libs/aiohttp/issues/7283>`\_

- Completed `trust_env` parameter description to honor `wss_proxy`,
`ws_proxy` or `no_proxy` env.

    `#&#8203;7325 <https://github.com/aio-libs/aiohttp/issues/7325>`\_

- Expanded SSL documentation with more examples (e.g. how to use
certifi). -- by :user:`Dreamsorcerer`

    `#&#8203;7334 <https://github.com/aio-libs/aiohttp/issues/7334>`\_

-   Fix, update, and improve client exceptions documentation.

    `#&#8203;7733 <https://github.com/aio-libs/aiohttp/issues/7733>`\_

## Deprecations and Removals

-   Added `shutdown_timeout` parameter to `BaseRunner`, while
deprecating `shutdown_timeout` parameter from `BaseSite`. -- by
:user:`Dreamsorcerer`

    `#&#8203;7718 <https://github.com/aio-libs/aiohttp/issues/7718>`\_

-   Dropped Python 3.6 support.

    `#&#8203;6378 <https://github.com/aio-libs/aiohttp/issues/6378>`\_

-   Dropped Python 3.7 support. -- by :user:`Dreamsorcerer`

    `#&#8203;7336 <https://github.com/aio-libs/aiohttp/issues/7336>`\_

- Removed support for abandoned `tokio` event loop. -- by
:user:`Dreamsorcerer`

    `#&#8203;7281 <https://github.com/aio-libs/aiohttp/issues/7281>`\_

## Misc

-   Made `print` argument in `run_app()` optional.

    `#&#8203;3690 <https://github.com/aio-libs/aiohttp/issues/3690>`\_

-   Improved performance of `ceil_timeout` in some cases.

    `#&#8203;6316 <https://github.com/aio-libs/aiohttp/issues/6316>`\_

- Changed importing Gunicorn to happen on-demand, decreasing import time
by ~53%. -- :user:`Dreamsorcerer`

    `#&#8203;6591 <https://github.com/aio-libs/aiohttp/issues/6591>`\_

- Improved import time by replacing `http.server` with
`http.HTTPStatus`.

    `#&#8203;6903 <https://github.com/aio-libs/aiohttp/issues/6903>`\_

- Fixed annotation of `ssl` parameter to disallow `True`. -- by
:user:`Dreamsorcerer`.

    `#&#8203;7335 <https://github.com/aio-libs/aiohttp/issues/7335>`\_

***

</details>

---

### 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.

---

- [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check
this box

---

This PR has been generated by [Mend
Renovate](https://www.mend.io/free-developer-tools/renovate/). View
repository job log
[here](https://developer.mend.io/github/allenporter/pyrainbird).

<!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNy41OS44IiwidXBkYXRlZEluVmVyIjoiMzcuNTkuOCIsInRhcmdldEJyYW5jaCI6Im1haW4ifQ==-->

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
@ralphm ralphm mentioned this pull request Mar 7, 2024
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bot:chronographer:provided There is a change note present in this PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants