-
Notifications
You must be signed in to change notification settings - Fork 57
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
native node async/await test #71
Comments
This looks relevant nodejs/node#20404 |
Looks like nodejs/node#20404 is a duplicate of nodejs/node#20274 One of the comments on 20274 says:
|
Turns out the code in #82 is necessary for at least early v10 usage (see #71 (comment)). We do need a better story about conditional/version-specific instrumentation? see #86. this PR reverts #82 and adds node 10.0.0 to the build matrix (which fails without this revert)
Hello, We will be closing this issue as it is a low priority for us. It is unlikely that we'll ever get to it, and so we'd like to set expectations accordingly. As we enter 2022 Q1, we are trimming our OSS backlog. This is so that we can focus better on areas that are more aligned with the OpenTelemetry-focused direction of telemetry ingest for Honeycomb. If this issue is important to you, please feel free to ping here and we can discuss/re-open. |
context doesn't seem to get propagated for native node async/await usage.
The text was updated successfully, but these errors were encountered: