Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.60%. Comparing base (1127bcd) to head (f8b0ed5).
Report is 2843 commits behind head on master.

@@            Coverage Diff             @@
##           master    #9530      +/-   ##
==========================================
+ Coverage   97.86%   98.60%   +0.73%     
==========================================
  Files         114      113       -1     
  Lines       35330    35295      -35     
  Branches     4238     4193      -45     
==========================================
+ Hits        34576    34802     +226     
+ Misses        563      331     -232     
+ Partials      191      162      -29     

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

CodSpeed Performance Report

Merging #9530 will not alter performance

_{Comparing Cycloctane:baseurl_with_path (f8b0ed5) with master (06b2398)}

Summary

✅ 5 untouched benchmarks

Formatting of the client reference block isn't great, but its an existing problem so not something that needs to be fixed here

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

❌ Failed to cleanly apply f3a3f60 on top of patchback/backports/3.11/f3a3f60b7a4b181272472b188e67d3b5f4ad3306/pr-9530

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

4. Now, cherry-pick PR Allow URLs with paths that end with / as base_url in ClientSession #9530 contents into that branch:

   $ git cherry-pick -x f3a3f60b7a4b181272472b188e67d3b5f4ad3306

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

   $ git cherry-pick -m1 -x f3a3f60b7a4b181272472b188e67d3b5f4ad3306

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Allow URLs with paths that end with / as base_url in ClientSession #9530 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/f3a3f60b7a4b181272472b188e67d3b5f4ad3306/pr-9530

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.