Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 97.93%. Comparing base (e0ff524) to head (27feace).
Report is 855 commits behind head on master.

@@            Coverage Diff             @@
##           master    #8636      +/-   ##
==========================================
+ Coverage   97.90%   97.93%   +0.02%     
==========================================
  Files         107      107              
  Lines       33471    33458      -13     
  Branches     3938     3936       -2     
==========================================
- Hits        32769    32766       -3     
+ Misses        518      510       -8     
+ Partials      184      182       -2     

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

I'm in the process of preparing .2 so I'll merge this one shortly unless there are any objections.

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

❌ Failed to cleanly apply 51d872e on top of patchback/backports/3.10/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636

Backporting merged PR #8636 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/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636 upstream/3.10

4. Now, cherry-pick PR Remove Request.wait_for_disconnection() method #8636 contents into that branch:

   $ git cherry-pick -x 51d872e1b87480b84a1a541af394a34b311ec22c

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

   $ git cherry-pick -m1 -x 51d872e1b87480b84a1a541af394a34b311ec22c

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove Request.wait_for_disconnection() method #8636 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636

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 51d872e on top of patchback/backports/3.11/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636

Backporting merged PR #8636 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/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636 upstream/3.11

4. Now, cherry-pick PR Remove Request.wait_for_disconnection() method #8636 contents into that branch:

   $ git cherry-pick -x 51d872e1b87480b84a1a541af394a34b311ec22c

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

   $ git cherry-pick -m1 -x 51d872e1b87480b84a1a541af394a34b311ec22c

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Remove Request.wait_for_disconnection() method #8636 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/51d872e1b87480b84a1a541af394a34b311ec22c/pr-8636

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.