Can we add a test to cover this case?

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.56%. Comparing base (2628256) to head (fd02612).
Report is 727 commits behind head on master.

@@           Coverage Diff           @@
##           master    #6653   +/-   ##
=======================================
  Coverage   98.56%   98.56%           
=======================================
  Files         107      107           
  Lines       34949    34981   +32     
  Branches     4139     4150   +11     
=======================================
+ Hits        34446    34478   +32     
  Misses        335      335           
  Partials      168      168           

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

Can we add a test to cover this case?

OK, will have a try.

Can we add a test to cover this case?

I had added a test: "test_https_connect_fingerprint_mismatch", please help to have a review, thanks!

Hi,

There remains one item: "Documentation reflects the changes" in the checklist not done yet. But I checked related document, seems there is no need to add document for this bug fix, any ideas?

Thanks!

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

❌ Failed to cleanly apply e3b1011 on top of patchback/backports/3.11/e3b1011f2146ad0faa4c3d3c29f26b73e1400564/pr-6653

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

4. Now, cherry-pick PR Fix issue 6652: Raise aiohttp.ServerFingerprintMismatch exception o… #6653 contents into that branch:

   $ git cherry-pick -x e3b1011f2146ad0faa4c3d3c29f26b73e1400564

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

   $ git cherry-pick -m1 -x e3b1011f2146ad0faa4c3d3c29f26b73e1400564

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Fix issue 6652: Raise aiohttp.ServerFingerprintMismatch exception o… #6653 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.11/e3b1011f2146ad0faa4c3d3c29f26b73e1400564/pr-6653

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.