-
Notifications
You must be signed in to change notification settings - Fork 277
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
Change AgentTracer.activeScope() to return AgentScope #2902
Conversation
dd-trace-ot/src/main/java/datadog/opentracing/CustomScopeManagerWrapper.java
Show resolved
Hide resolved
c1edd43
to
2b9a9b5
Compare
0e23627
to
820d7f2
Compare
dd-trace-ot/src/test/groovy/datadog/opentracing/CustomScopeManagerTest.groovy
Show resolved
Hide resolved
820d7f2
to
ed639c2
Compare
} else { | ||
return new OTScopeManager.OTScope((AgentScope) scope, finishSpanOnClose, this); | ||
return new CustomScope(scope); |
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.
@mcculls I'm wondering what the reason for this change was?
|
||
@Override | ||
public AgentSpan span() { | ||
return toAgentSpan(delegate.span()); |
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.
Unfortunately adding this class makes dd-trace-ot fail compile time checks for Graalvm because of this call when using opentracing 0.33, because Scope.span()
was removed. Even if this code can never actually be executed
This changes a number of internal APIs and some non-public types in
dd-trace-ot
It also updates a test to check that internal scopes are handled correctly when a custom scope manager is used.