-
-
Notifications
You must be signed in to change notification settings - Fork 432
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
Performance: Refactor resolving SpanContext for Throwable #1068
Conversation
Codecov Report
@@ Coverage Diff @@
## main #1068 +/- ##
============================================
- Coverage 73.17% 72.71% -0.47%
+ Complexity 1542 1516 -26
============================================
Files 162 161 -1
Lines 5510 5461 -49
Branches 562 548 -14
============================================
- Hits 4032 3971 -61
- Misses 1189 1199 +10
- Partials 289 291 +2
Continue to review full report at Codecov.
|
@bruno-garcia @marandaneto please take a look. |
As far as I can tell covecov reports are broken. Since we have a check for code coverage in gradle build already, could we turn it off? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
📢 Type of change
📜 Description
Refactor resolving SpanContext for Throwable
💡 Motivation and Context
Previous implementation would fail once we switch to sending individual spans. Here we keep an association between throwable and SpanContext on the
Hub
which is independent from transaction or span being still in memory.💚 How did you test it?
Integration tests cover it.
📝 Checklist