Roch Devost

@jamesone How are you initializing dd-trace? Also, did you add our ESM loader to the CLI arguments?

For context, here is a bit of history behind this issue since it's been problematic for a while now. Historically, context propagation APIs for Node have been using monkey patching...

Progress for the v8 change can be tracked [here](https://chromium-review.googlesource.com/c/v8/v8/+/2466783).

Progress on the Node side can be tracked in https://github.com/nodejs/node/pull/36394

> Here u set the destroy hook The `async_hooks` scope manager is only used in old versions of Node. Any recent versions such as latest 12.x, 14.x or 16.x use...

cc @Qard who would have the most insight to determine at a glance if there could be a regression causing this issue.

@stephenh I'm able to reproduce with the project you've shared, but without being able to debug and with a codebase I don't know it's difficult to try to find the...

Possible cause of the new issue since 16.2.0: https://github.com/nodejs/node/issues/38781

> And with the previous implementation, git would be called a few times for each test, which causes dramatic slowdowns when there are thousands of tests @juan-fernandez Doesn't this actually...

@juan-fernandez Do we have any existing benchmarks that would help quantify the difference and avoid future regressions?