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

Fix clobbering of the span context if extraction fails #656

Merged
merged 3 commits into from Apr 27, 2020

Conversation

krnowak
Copy link
Member

@krnowak krnowak commented Apr 23, 2020

Closes #655.

api/trace/testtrace/propagator_test.go Outdated Show resolved Hide resolved
Copy link
Contributor

@seh seh left a comment

Choose a reason for hiding this comment

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

Thank you for responding to the issue I filed so quickly.

api/trace/trace_context_propagator.go Show resolved Hide resolved
api/trace/b3_propagator.go Show resolved Hide resolved
api/trace/testtrace/propagator_test.go Outdated Show resolved Hide resolved
api/trace/testtrace/propagator_test.go Show resolved Hide resolved
api/trace/testtrace/propagator_test.go Show resolved Hide resolved
This causes problems if multiple trace propagators are chained,
because the first propagator in chain may extract a valid span
context, then next propagator will overwrite it with an empty span
context when required headers in supplier are missing.
@krnowak
Copy link
Member Author

krnowak commented Apr 27, 2020

Updated and rebased.

@jmacd jmacd merged commit c23e09c into open-telemetry:master Apr 27, 2020
@krnowak krnowak deleted the prop-bug branch April 27, 2020 20: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.

api/trace: Neither B3.Extract nor TraceContext.Extract stack properly after other HTTPExtractors
4 participants