Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.30%. Comparing base (11a96fc) to head (7dc471b).
Report is 59 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff           @@
##           master    #9064   +/-   ##
=======================================
  Coverage   98.30%   98.30%           
=======================================
  Files         107      107           
  Lines       34371    34371           
  Branches     4072     4072           
=======================================
  Hits        33787    33787           
  Misses        412      412           
  Partials      172      172           

☔ 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 7b11e23 on top of patchback/backports/3.10/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064

Backporting merged PR #9064 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/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064 upstream/3.10

4. Now, cherry-pick PR Fix sendfile test fixture #9064 contents into that branch:

   $ git cherry-pick -x 7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1

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

   $ git cherry-pick -m1 -x 7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix sendfile test fixture #9064 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064

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 7b11e23 on top of patchback/backports/3.11/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064

Backporting merged PR #9064 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/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064 upstream/3.11

4. Now, cherry-pick PR Fix sendfile test fixture #9064 contents into that branch:

   $ git cherry-pick -x 7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1

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

   $ git cherry-pick -m1 -x 7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix sendfile test fixture #9064 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/7b11e234aee86aba2ef24c4e0664dcd0b9fe8cd1/pr-9064

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.

3.10 #9224
3.11 #9225