Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.42%. Comparing base (3c1ca45) to head (2c56bb0).
Report is 1050 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master    #9239   +/-   ##
=======================================
  Coverage   98.42%   98.42%           
=======================================
  Files         107      107           
  Lines       34699    34741   +42     
  Branches     4111     4121   +10     
=======================================
+ Hits        34152    34194   +42     
  Misses        380      380           
  Partials      167      167           

☔ 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 63cfd5f on top of patchback/backports/3.10/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239

Backporting merged PR #9239 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/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239 upstream/3.10

4. Now, cherry-pick PR Stop raise_for_status() releasing when in a context #9239 contents into that branch:

   $ git cherry-pick -x 63cfd5f96b3ce819c7feac67dfa4183ac4731acd

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

   $ git cherry-pick -m1 -x 63cfd5f96b3ce819c7feac67dfa4183ac4731acd

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Stop raise_for_status() releasing when in a context #9239 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239

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 63cfd5f on top of patchback/backports/3.11/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239

Backporting merged PR #9239 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/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239 upstream/3.11

4. Now, cherry-pick PR Stop raise_for_status() releasing when in a context #9239 contents into that branch:

   $ git cherry-pick -x 63cfd5f96b3ce819c7feac67dfa4183ac4731acd

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

   $ git cherry-pick -m1 -x 63cfd5f96b3ce819c7feac67dfa4183ac4731acd

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Stop raise_for_status() releasing when in a context #9239 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/63cfd5f96b3ce819c7feac67dfa4183ac4731acd/pr-9239

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.