Chris Karcher

I'm not 100% if it's the same thing, but this might be related to #2090.

This is the same issue described in #9978 that I think was mistakenly marked as fixed. The issue still exists, and we have to work around it by wiring up...

Right - in your first example, the `{ parseAs: '...' }` triggered Fastify to consume the body prior to passing it to your handler, which mean that Next.js would continue...

@saihaj - could you take a look at this PR when you have a moment? A similar had been submitted and approved previously (so it might look familiar), but I...

@dyladan - thanks for adding the `up-for-grabs` label. Does that imply that you're in support of this feature request? If so, I can take a stab at the implementation. I...

Thanks, @vmarchaud! I'll take a stab at the implementation early this week. My only question at this point is how to make this change in a backwards compatible way (see...

> **My question - is there a precedent in the otel JS libs for doing a safe/optional import that attempts to import something (e.g., a function), but doesn't blow up...

> I believe it would be better to add utils/properties to the BaggageEntryMetadata type I'd originally considered adding it to `BaggageEntryMetadata` and doing the deserialization within [baggageEntryMetadataFromString()](https://github.com/open-telemetry/opentelemetry-js-api/blob/main/src/baggage/utils.ts#L41), but it felt...

@legendecas @vmarchaud - can we please keep this issue open? #2766 was only the first part of the fix. I still need to submit a PR to `@opentelemetry/api` to expose...

@IvanGoncharov - I finally worked through the EasyCLA issues, would you mind taking a look at this PR?