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

compat: fix UberTraceContext extraction #24

Merged
merged 3 commits into from
Jul 12, 2024
Merged

Conversation

wade-arista
Copy link
Contributor

When we were extracing the span context from an uber-trace-id header, we didn't properly handle the case of flags=0. It was expecting, for the flags, a hex encoded string, but in fact, the flags is just a base 16 integer field.

The correct conversion is to just use ParseInt with base 16.

The test cases are taken from topic manager examples using the jaeger client with go-opentracing.

When we were extracing the span context from an uber-trace-id header,
we didn't properly handle the case of flags=0. It was expecting, for
the flags, a hex encoded string, but in fact, the flags is just a base
16 integer field.

The correct conversion is to just use ParseInt with base 16.

The test cases are taken from topic manager examples using the jaeger
client with go-opentracing.
uber.go Outdated Show resolved Hide resolved
@wade-arista wade-arista merged commit c5e2c12 into main Jul 12, 2024
1 check passed
@wade-arista wade-arista deleted the wade.fixUberOtelExtract branch July 12, 2024 23:19
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.

2 participants