Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.27%. Comparing base (cc6d763) to head (77a8c13).
Report is 1072 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master    #8951   +/-   ##
=======================================
  Coverage   98.27%   98.27%           
=======================================
  Files         107      107           
  Lines       34226    34239   +13     
  Branches     4058     4061    +3     
=======================================
+ Hits        33637    33650   +13     
  Misses        416      416           
  Partials      173      173           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

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

❌ Failed to cleanly apply 45d6e4f on top of patchback/backports/3.10/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951

Backporting merged PR #8951 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.10/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951 upstream/3.10

4. Now, cherry-pick PR Avoid logging exception from run_app() that is also raised #8951 contents into that branch:

   $ git cherry-pick -x 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125

   If it'll yell at you with something like fatal: Commit 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Avoid logging exception from run_app() that is also raised #8951 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951

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.

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

❌ Failed to cleanly apply 45d6e4f on top of patchback/backports/3.11/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951

Backporting merged PR #8951 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.11/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951 upstream/3.11

4. Now, cherry-pick PR Avoid logging exception from run_app() that is also raised #8951 contents into that branch:

   $ git cherry-pick -x 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125

   If it'll yell at you with something like fatal: Commit 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125 is a merge but no -m option was given., add -m 1 as follows instead:

   $ git cherry-pick -m1 -x 45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Avoid logging exception from run_app() that is also raised #8951 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/45d6e4f14572bfc4cfc3f32a2c7c72a9cc28f125/pr-8951

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.