Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.32%. Comparing base (8911419) to head (57344db).
Report is 1064 commits behind head on master.

✅ All tests successful. No failed tests found.

@@           Coverage Diff            @@
##           master    #9203    +/-   ##
========================================
  Coverage   98.31%   98.32%            
========================================
  Files         107      107            
  Lines       34510    34635   +125     
  Branches     4100     4113    +13     
========================================
+ Hits        33929    34055   +126     
  Misses        410      410            
+ Partials      171      170     -1     

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

Running well on production overnight 👍

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

❌ Failed to cleanly apply 6e70c0a on top of patchback/backports/3.10/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203

Backporting merged PR #9203 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/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203 upstream/3.10

4. Now, cherry-pick PR Implement heapq for cookie expire times #9203 contents into that branch:

   $ git cherry-pick -x 6e70c0ab91f383a0d28448d1506d826a9b44e53d

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

   $ git cherry-pick -m1 -x 6e70c0ab91f383a0d28448d1506d826a9b44e53d

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Implement heapq for cookie expire times #9203 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.10/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203

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 6e70c0a on top of patchback/backports/3.11/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203

Backporting merged PR #9203 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/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203 upstream/3.11

4. Now, cherry-pick PR Implement heapq for cookie expire times #9203 contents into that branch:

   $ git cherry-pick -x 6e70c0ab91f383a0d28448d1506d826a9b44e53d

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

   $ git cherry-pick -m1 -x 6e70c0ab91f383a0d28448d1506d826a9b44e53d

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Implement heapq for cookie expire times #9203 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/6e70c0ab91f383a0d28448d1506d826a9b44e53d/pr-9203

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.