Codecov Report

Merging #7503 (30cfeba) into master (c9176ac) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7503   +/-   ##
=======================================
  Coverage   97.33%   97.33%           
=======================================
  Files         106      106           
  Lines       31452    31452           
  Branches     3571     3571           
=======================================
  Hits        30615    30615           
  Misses        634      634           
  Partials      203      203           

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

Thanks, looks like it could be some time before there's a new uvloop, so seems good to me.

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

❌ Failed to cleanly apply 53373c4 on top of patchback/backports/3.9/53373c49aaf57c0239bb26046effbf2159102eb0/pr-7503

Backporting merged PR #7503 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.9/53373c49aaf57c0239bb26046effbf2159102eb0/pr-7503 upstream/3.9

4. Now, cherry-pick PR Skip uvloop install on Python 3.12 #7503 contents into that branch:

   $ git cherry-pick -x 53373c49aaf57c0239bb26046effbf2159102eb0

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

   $ git cherry-pick -m1 -x 53373c49aaf57c0239bb26046effbf2159102eb0

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Skip uvloop install on Python 3.12 #7503 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.9/53373c49aaf57c0239bb26046effbf2159102eb0/pr-7503

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.