Add benchmark for JSON post requests that check the content type #10553
+27
−0
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
bdraco
added
bot:chronographer:skip
CodSpeed Performance ReportMerging #10553 will not alter performanceComparing Summary
Benchmarks breakdown
|
Codecov ReportAll modified and coverable lines are covered by tests ✅
✅ All tests successful. No failed tests found. Additional details and impacted files@@ Coverage Diff @@
## master #10553 +/- ##
=======================================
Coverage 98.69% 98.69%
=======================================
Files 122 122
Lines 37230 37246 +16
Branches 2064 2065 +1
=======================================
+ Hits 36745 36761 +16
Misses 338 338
Partials 147 147
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #10554 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Mar 15, 2025
) (cherry picked from commit 55c5f1f)
Backport to 3.12: 💚 backport PR created✅ Backport PR branch: Backported as #10555 🤖 @patchback |
patchback bot
pushed a commit
that referenced
this pull request
Mar 15, 2025
) (cherry picked from commit 55c5f1f)
bdraco
added a commit
that referenced
this pull request
Mar 15, 2025
…sts that check the content type (#10554) **This is a backport of PR #10553 as merged into master (55c5f1f).** <!-- Thank you for your contribution! --> ## What do these changes do? Add benchmark for JSON post requests that check the content type ## Are there changes in behavior for the user? no ## Is it a substantial burden for the maintainers to support this? no Co-authored-by: J. Nick Koston <nick@koston.org>
bdraco
added a commit
that referenced
this pull request
Mar 15, 2025
…sts that check the content type (#10555) **This is a backport of PR #10553 as merged into master (55c5f1f).** <!-- Thank you for your contribution! --> ## What do these changes do? Add benchmark for JSON post requests that check the content type ## Are there changes in behavior for the user? no ## Is it a substantial burden for the maintainers to support this? no Co-authored-by: J. Nick Koston <nick@koston.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What do these changes do?
Add benchmark for JSON post requests that check the content type
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no