v5.117.0 proposal - #9505
Conversation
Bumps the test-versions group with 1 update in the /packages/dd-trace/test/plugins/versions directory: [pnpm](https://github.com/pnpm/pnpm/tree/HEAD/pnpm11/pnpm). Updates `pnpm` from 11.15.0 to 11.15.1 - [Release notes](https://github.com/pnpm/pnpm/releases) - [Commits](https://github.com/pnpm/pnpm/commits/v11.15.1/pnpm11/pnpm) --- updated-dependencies: - dependency-name: pnpm dependency-version: 11.15.1 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: test-versions ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
* fix(test-optimization): complete test runs after subscriber loss
Finish subscribers can disable themselves while handling a diagnostic-channel publication, leaving no callback owner and hanging the framework run indefinitely. Treat losing the last subscriber as completion while preserving exporter-backed waits and Jest's timeout.
* test(test-optimization): cover vitest suite finish and cucumber config-loss
The vitest worker suite-finish path (the one that awaits the flush through the
shared channel helper) had no dedicated instrumentation spec and no CI job, so
its subscriber-loss behavior rode only on end-to-end coverage. Add a real-path
spec driving the `@vitest/runner` `startTests` hook, plus `instrumentation-vitest`
and `instrumentation-cucumber` jobs alongside the other frameworks.
The cucumber spec now pins the `|| {}` guard in getWrappedStart: a
library-configuration subscriber that disables itself without responding resolves
the request to `undefined`, and the run must still finish with every remote
feature treated as disabled.
Drive-by fix:
* Drop `frameworkVersion` from the vitest worker `testSuiteFinishCh` payload; the
suite-finish subscriber never reads it and it is already carried in currentStore.
* fix(test-optimization): finish runs after plugin lifecycle errors
Mocha configuration requests publish through runStores, so an internal handler error can disable the plugin and leave delayed startup waiting forever. Re-enabling Playwright after test start can leave an active finish subscriber without a span, whose early return similarly never releases the worker.
…9501) * feat(profiling): pack column numbers for server-side unminification Updates profiler to 5.17.0, and then sets columnNumbers: 'pack' on the wall profiler and pass 'pack' to the space profiler's heap.profile call. pprof 5.17.0 packs the column into the line only for frames whose source map is declared but missing (dd:has-missing-map-files) — exactly the frames sent for server-side unminification — so this lets the backend deobfuscate minified Node.js (e.g. Next.js server) frames, where the column is the only discriminator between functions on a single generated line.
Overall package sizeSelf size: 7.49 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------| | import-in-the-middle | 3.3.2 | 124.41 kB | 440.65 kB | | opentracing | 0.14.7 | 194.81 kB | 194.81 kB | | dc-polyfill | 0.1.11 | 25.74 kB | 25.74 kB |🤖 This report was automatically generated by heaviest-objects-in-the-universe |
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 15f08de | Docs | Datadog PR Page | Give us feedback! |
BenchmarksBenchmark execution time: 2026-07-23 11:51:58 Comparing candidate commit 15f08de in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 2325 metrics, 33 unstable metrics.
|
Features
Fixes
Internal (CI, Testing, Benchmarking)