Valentin Marchaud

> Am I correct in understanding that browsers today (and maybe for the foreseeable future) don't offer a way to maintain context across native async/await, and so there's no way...

I can't find a place where SDK documentation is on the website, maybe @svrnm or @cartermp can help ?

I'm not sure to understand why running those tests in arm64 would change anything, node itself support amd64 so running tests on amd64 doesn't change anything AFAIK

I agree that we should not decaclare them stable (althrough i don't think there is plan to declare any instrumentations stable yet ?), specially with the RUM SIG that will...

I'm not sure with this is required for GA cc @dyladan @obecny

I know there was some discussion around user intereaction instrumentation about how to map to spans (https://github.com/open-telemetry/opentelemetry-js-contrib/pull/980, https://github.com/open-telemetry/opentelemetry-js-contrib/pull/743). Honestly i feel its much better to keep them contrib until the...

> . The ask is only to move them into experimental folder since they instrumentations are not for 3rd party libraries. There are packages for non-3rd party libraries in contrib...

Did you try to reproduce by only using zone.js ? Seems likely that the problem comes from zonejs instead of our implementation

> @vmarchaud since you already started looking into this can you take this issue? I answered because someone on slack asked a similar question few days ago (https://cloud-native.slack.com/archives/C01NL1GRPQR/p1660673184710719). I honestly...

Not currently, but this shouldn't be too hard to implement by extending the batch exporter there: https://github.com/open-telemetry/opentelemetry-js/blob/main/packages/opentelemetry-sdk-trace-base/src/export/BatchSpanProcessorBase.ts