-
Notifications
You must be signed in to change notification settings - Fork 127
Reorder inheritance on span nodes #1539
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
base: main
Are you sure you want to change the base?
Conversation
✅MegaLinter analysis: Success
See detailed reports in MegaLinter artifacts |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1539 +/- ##
===========================================
- Coverage 81.72% 71.51% -10.21%
===========================================
Files 207 207
Lines 23909 23904 -5
Branches 3789 3789
===========================================
- Hits 19540 17096 -2444
- Misses 3098 5274 +2176
- Partials 1271 1534 +263 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Core tracing will be adding a bunch of logic to the span_event method which is called via super on inheriting classes before those inheriting classes add additional attributes. In order for the core tracing logic to work correctly, this inheritance call order has to be reversed; the inheriting classes must first add the attributes and THEN call super.
01341fa
to
2fcf966
Compare
This is more of a general question: Originally, |
…ic-python-agent into reorder-node-super-calls
Overview
Core tracing will be adding a bunch of logic to the span_event method which is called via super on inheriting classes before those inheriting classes add additional attributes. In order for the core tracing logic to work correctly, this inheritance call order has to be reversed; the inheriting classes must first add the attributes and THEN call super.