-
-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid tracing overhead in http_writer when there are no traces #9031
Conversation
If there are not traces set for the request, we would still create partial functions in ClientRequest and call them in http_writer
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 #9031 +/- ##
=======================================
Coverage 98.30% 98.30%
=======================================
Files 107 107
Lines 34355 34355
Branches 4066 4066
=======================================
Hits 33771 33771
Misses 412 412
Partials 172 172
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.10: 💚 backport PR created✅ Backport PR branch: Backported as #9045 🤖 @patchback |
(cherry picked from commit 9f0ae07)
Backport to 3.11: 💚 backport PR created✅ Backport PR branch: Backported as #9046 🤖 @patchback |
(cherry picked from commit 9f0ae07)
…ter when there are no traces (#9045) Co-authored-by: J. Nick Koston <nick@koston.org>
…ter when there are no traces (#9046) Co-authored-by: J. Nick Koston <nick@koston.org>
What do these changes do?
If there are not traces set for the request, we would still create partial functions in ClientRequest and call them in http_writer
Are there changes in behavior for the user?
no
Is it a substantial burden for the maintainers to support this?
no
before
after