Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.83%. Comparing base (21d640d) to head (726ee82).
Report is 1 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master   #11114   +/-   ##
=======================================
  Coverage   98.83%   98.83%           
=======================================
  Files         129      129           
  Lines       41763    41763           
  Branches     2245     2245           
=======================================
  Hits        41276    41276           
  Misses        337      337           
  Partials      150      150           

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

CodSpeed Performance Report

Merging #11114 will not alter performance

_{Comparing downgrade_logging (726ee82) with master (21d640d)}

Summary

✅ 59 untouched benchmarks

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

❌ Failed to cleanly apply 758738e on top of patchback/backports/3.12/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114

Backporting merged PR #11114 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.12/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114 upstream/3.12

4. Now, cherry-pick PR Downgrade connector close error to debug #11114 contents into that branch:

   $ git cherry-pick -x 758738ed4d2a3c3d2c74b9d8ba217c7141af1a16

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

   $ git cherry-pick -m1 -x 758738ed4d2a3c3d2c74b9d8ba217c7141af1a16

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Downgrade connector close error to debug #11114 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.12/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114

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.13: 💔 cherry-picking failed — conflicts found

❌ Failed to cleanly apply 758738e on top of patchback/backports/3.13/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114

Backporting merged PR #11114 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.13/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114 upstream/3.13

4. Now, cherry-pick PR Downgrade connector close error to debug #11114 contents into that branch:

   $ git cherry-pick -x 758738ed4d2a3c3d2c74b9d8ba217c7141af1a16

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

   $ git cherry-pick -m1 -x 758738ed4d2a3c3d2c74b9d8ba217c7141af1a16

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Downgrade connector close error to debug #11114 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.13/758738ed4d2a3c3d2c74b9d8ba217c7141af1a16/pr-11114

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.