Chris Karcher

Fix crash in node when mixing sync/async resolvers (backport of #3529)

16

Fixes #3528 This PR is a clone of #3529, which is currently held up by CLA approvals. Full credit goes to @asztal for identifying and fixing the underlying issue. @hobby203,...

Fix crash in node when mixing sync/async resolvers (backport of #3529)

5

This is a backport of ~#3529~ #3651 to the `15.x` branch that fixes #3528. Full credit to @asztal for identifying the fix and submitting the original PR.

Fix crash in node when mixing sync/async resolvers (backport of #3529)

6

This is a backport of ~#3529~ #3651 to the `16.x` branch that fixes #3528. Full credit to @asztal for identifying the fix and submitting the original PR.

Fastify: next.js attempts (and fails) to consume a request body that's already been consumed by Fastify

5

### What version of Next.js are you using? 10.2.0 ### What version of Node.js are you using? 14.15.4 ### What browser are you using? Chrome ### What operating system are...

Fixes #3528 in the `16.x.x` branch.

Fixes #3528 in the `15.x.x` branch

Fix crash in node when mixing sync/async resolvers

1

Fixes #3528 Ensures that if `executeFields` encounters a mix of promises and thrown errors, the promises will be awaited before throwing the error.

Add `properties` field to the `BaggageEntry` interface

9

### Is your feature request related to a problem? Please describe. The `opentelemetry-js` package currently adheres to the [`key`](https://w3c.github.io/baggage/#key) and [`value`](https://w3c.github.io/baggage/#value) definitions in the W3C baggage spec. However, the W3C...