B3 Propagator should left-pad 64-bit trace IDs with zeros #1020
Assignees
Labels
bug
Something isn't working
Comments
pichlermarc
pushed a commit
to dynatrace-oss-contrib/opentelemetry-js
that referenced
this issue
Dec 15, 2023
* chore: harmonize dependencies Harmonize dependencies by using following rules: * peer and dev depend on API ^1.0.0 (like in core repo) * depend on SDK ^1.0.0 (don't limit user) * dev-depend on latest SDK pinned (like other deps) * pin dependencies within the lerna project (like in core repo) * chore: re-add shimmer
martinkuba
pushed a commit
to martinkuba/opentelemetry-js
that referenced
this issue
Mar 13, 2024
* chore: harmonize dependencies Harmonize dependencies by using following rules: * peer and dev depend on API ^1.0.0 (like in core repo) * depend on SDK ^1.0.0 (don't limit user) * dev-depend on latest SDK pinned (like other deps) * pin dependencies within the lerna project (like in core repo) * chore: re-add shimmer
martinkuba
pushed a commit
to martinkuba/opentelemetry-js
that referenced
this issue
Mar 16, 2024
* chore: harmonize dependencies Harmonize dependencies by using following rules: * peer and dev depend on API ^1.0.0 (like in core repo) * depend on SDK ^1.0.0 (don't limit user) * dev-depend on latest SDK pinned (like other deps) * pin dependencies within the lerna project (like in core repo) * chore: re-add shimmer
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Please answer these questions before submitting a bug report.
What version of OpenTelemetry are you using?
HEAD
What version of Node are you using?
N/A
What did you do?
Provide a 64-bit trace ID in a B3 header.
What did you expect to see?
The 64-bit trace ID left-padded with zeros in the
SpanContext.What did you see instead?
The
SpanContextis not propagated as the validation regexp only allows for 32 hex digit trace IDs.Additional context
See open-telemetry/opentelemetry-go#686
The text was updated successfully, but these errors were encountered: