Marc Pichler

Is this also happening without OTel instrumentation registered? The stack-trace and the error actually suggest that `/home/webapp/.aws/config` does not exist. It is natural for OTel to turn up in the...

> Is this also happening without OTel instrumentation registered? @aschuhl any update on the requested info? Otherwise we'll likely not be able to help.

@Clement-Stauner thanks for reaching out. I've tried reproducing this (https://github.com/pichlermarc/repro-4489) but I'm not sure I'm missing something. Would you mind trying to remove `node_modules` and `package-lock.json` and trying again with...

Ah I see. This is actually reproducible with `"exactOptionalPropertyTypes": true`, which is not included in `strict` by default (because turning it on does cause a lot of churn for existing...

Closing as duplicate of #3713. We've discussed it in the SIG meeting last week, and we're generally in favor of changing to `"exactOptionalPropertyTypes": true`. PRs for this are welcome, for...

Re-categorizing as a feature as we don't expect any of our packages to work with bun. We're happy to accept a PR if that's the only change needed to get...

We currently don't have a node-based fetch instrumentation, so that's why there's no propagation. Re-categorizing this as a feature-request.

Closing this as the new undici instrumentation is now available: https://www.npmjs.com/package/@opentelemetry/instrumentation-undici node-fetch uses `undici` under the hood so using this one should also enable you to propagate context using node-fetch...

Hmm, I think I'm missing some context on the use-case of this. :thinking: Possibly a naive theory on my end, but I'd assume that most request's bodies will contain data...

> If we went the route of adding it to a span in our application then it wouldn't be directly tied to the network span that we are tracing. The...