Marc Pichler

It's yours :slightly_smiling_face:

I can work on this :slightly_smiling_face:

Closing this as it has been fixed by #3133. Thank you for providing the reproducer! :slightly_smiling_face:

Hi @itai-codefresh, thanks for reporting this. Do you have a way to reproduce this issue? :thinking: If so, could you please open a [bug ticket](https://github.com/open-telemetry/opentelemetry-js/issues/new?assignees=&labels=bug%2Ctriage&template=bug_report.yaml) so that we can take...

Current progress is that metrics are updated to `InstrumentationScope`, but traces are not. I'm unassigning myself for now in case someone else has some cycles and wants to work on...

Is this a feature request for the `@opentelemetry/sdk-node` package? There is a propagator API that let's you set propagators independently of whether you're using trace or logs.

That depends on what you mean by it "instrument Propagation" :thinking: Instrumentations use the Propagator API and the Context API to propagate W3C trace context for example. For that to...

@cpatti97100 `@opentelemetry/instrumentation-fetch` is not intended for use with Node.js, does removing it get rid of the memory leak? :thinking:

> > @cpatti97100 `@opentelemetry/instrumentation-fetch` is not intended for use with Node.js, does removing it get rid of the memory leak? 🤔 > > it does, but here #4063 I read...

@cpatti97100 we've published the undici instrumentation recently. Would you be able to test that one out? :slightly_smiling_face: