CodSpeed Performance Report

Merging #11580 will not alter performance

_{Comparing sgaist:10889-default-content-type (801396c) with master (b1bd65d)}

Summary

✅ 59 untouched

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 98.74%. Comparing base (b1bd65d) to head (801396c).
⚠️ Report is 283 commits behind head on master.

@@            Coverage Diff             @@
##           master   #11580      +/-   ##
==========================================
+ Coverage   98.72%   98.74%   +0.01%     
==========================================
  Files         127      127              
  Lines       43449    43467      +18     
  Branches     2326     2327       +1     
==========================================
+ Hits        42896    42922      +26     
+ Misses        395      389       -6     
+ Partials      158      156       -2     

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

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

❌ Failed to cleanly apply d261f8a on top of patchback/backports/3.13/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580

Backporting merged PR #11580 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.13/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580 upstream/3.13

4. Now, cherry-pick PR Ensure that application/octet-stream is the default content_type #11580 contents into that branch:

   $ git cherry-pick -x d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc

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

   $ git cherry-pick -m1 -x d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Ensure that application/octet-stream is the default content_type #11580 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.13/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580

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 d261f8a on top of patchback/backports/3.14/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580

Backporting merged PR #11580 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/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580 upstream/3.14

4. Now, cherry-pick PR Ensure that application/octet-stream is the default content_type #11580 contents into that branch:

   $ git cherry-pick -x d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc

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

   $ git cherry-pick -m1 -x d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc

5. At this point, you'll probably encounter some merge conflicts. You must
   resolve them in to preserve the patch from PR Ensure that application/octet-stream is the default content_type #11580 as close to the
   original as possible.
6. Push this branch to your fork on GitHub:

   $ git push origin patchback/backports/3.14/d261f8a3ceaeb9699c13d6f62be9ea875f6f40bc/pr-11580

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.

Thanks for that fix. If you could create the backports with the above instructions, that'd be great, otherwise I'll look at them later in the week.

You're welcome !

Backport PR created :-)