Skip to content
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

Update to OpenTracing 0.33 #360

Merged
merged 2 commits into from Jan 15, 2021
Merged

Conversation

Ladicek
Copy link
Contributor

@Ladicek Ladicek commented Jan 14, 2021

No description provided.

@Ladicek Ladicek requested a review from a team as a code owner January 14, 2021 17:16
@Ladicek Ladicek added this to the 5.0.0 milestone Jan 14, 2021
radcortez
radcortez previously approved these changes Jan 14, 2021
return () -> {
Scope propagated = scopeManager.activate(span, false);
Scope propagated = scopeManager.activate(span);
return propagated::close;
};
}
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm looking at this again and I found this a bit weird. If the original thread had an active span, but not an active scope, the new thread will have the same active span, but it will also have an active scope.

I have read through opentracing/opentracing-java#267 and opentracing/opentracing-java#291 and it seems to me that OpenTracing just actively fights against our progamming model :-)

But I guess there's nothing better that we could do.

@Ladicek Ladicek merged commit 759661e into smallrye:master Jan 15, 2021
@Ladicek Ladicek deleted the opentracing-0.33 branch January 15, 2021 09:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants