v0.12.1#158
Merged
Merged
Conversation
The TraceExporterBuilder set url/service/env/hostname/app_version but never called set_runtime_id, so at build_async the builder fell back to Uuid::new_v4(). That gave the trace payload a random runtime-id that mismatched the stats payload (correlation bug) and called getrandom, which traps on wasm runtimes without a configured entropy source (surfaced as native-spans System Tests / E2E failures). Pass through the runtime-id the caller already provides.
ekump
approved these changes
Jul 2, 2026
Overall package sizeSelf size: 30.08 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.12.1
Patch release backporting the pipeline exporter runtime-id fix onto the 0.12.x line.
Included
fix(pipeline): set exporter runtime-id from the tracer— theTraceExporterBuildernever calledset_runtime_id, so it defaulted toUuid::new_v4()atbuild_async. That gave the trace payload a random runtime-id mismatching the stats payload (correlation bug) and calledgetrandom, which traps on wasm runtimes without an entropy source (surfaced as widespread native-spans System Tests / E2E failures in dd-trace-js — the pipeline trapped at exporter build, so no spans exported).Verification (on the 0.12.0 base)
node --test --test-force-exit test/pipeline.js→ 45/45node --test --test-force-exit test/http_transport.js→ 6/6Rebase-and-merge (matching the v0.x release-branch convention) to publish 0.12.1.