Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.01%. Comparing base (8c8906a) to head (6c337b7).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

@@            Coverage Diff             @@
##           master   #13501      +/-   ##
==========================================
+ Coverage   99.00%   99.01%   +0.01%     
==========================================
  Files         132      132              
  Lines       49635    49813     +178     
  Branches     2575     2587      +12     
==========================================
+ Hits        49141    49323     +182     
+ Misses        370      368       -2     
+ Partials      124      122       -2     

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

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

_{Reviews (3): Last reviewed commit: "Merge branch 'fix-tail-cap' of github.co..." | Re-trigger Greptile}

Merging this PR will not alter performance

✅ 84 untouched benchmarks
⏩ 83 skipped benchmarks¹

_{Comparing fix-tail-cap (6c337b7) with master (8c8906a)²}

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

❌ Failed to cleanly apply c207cad on top of patchback/backports/3.15/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501

Backporting merged PR #13501 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.15/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501 upstream/3.15

4. Now, cherry-pick PR Fix limit on message tail #13501 contents into that branch:

   $ git cherry-pick -x c207cadb257e0959b192ffca0548eca8c71eb96a

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

   $ git cherry-pick -m1 -x c207cadb257e0959b192ffca0548eca8c71eb96a

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

   $ git push origin patchback/backports/3.15/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501

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

❌ Failed to cleanly apply c207cad on top of patchback/backports/3.14/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501

Backporting merged PR #13501 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.14/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501 upstream/3.14

4. Now, cherry-pick PR Fix limit on message tail #13501 contents into that branch:

   $ git cherry-pick -x c207cadb257e0959b192ffca0548eca8c71eb96a

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

   $ git cherry-pick -m1 -x c207cadb257e0959b192ffca0548eca8c71eb96a

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

   $ git push origin patchback/backports/3.14/c207cadb257e0959b192ffca0548eca8c71eb96a/pr-13501

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.