-
Notifications
You must be signed in to change notification settings - Fork 804
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
[plugin-http] null-check socket before destructuring #1377
Comments
@OlivierAlbertini can you look into this? It looks like the typings say that |
I will look into this today |
@dyladan Hey, any updates on this? |
@OlivierAlbertini Do you have any idea what might have happened here? |
also seen with node 14 with
|
…-telemetry#1377) * fix(instrumentation-dns): fix instrumentation of `dns/promises` * chore(instrumentation-dns): fix ts error * Revert "fix(instrumentation-dns): fix instrumentation of `dns/promises`" This reverts commit a897248c5aac03573112cad093322cf5ab99ac17. * fix(instrumentation-dns): fix instrumentation of `dns/promises` * chore(instrumentation-dns): skip `dns/promises` test on node 14 * chore(instrumentation-dns): fix `dns/promises` test in ci --------- Co-authored-by: Amir Blum <amirgiraffe@gmail.com>
What version of OpenTelemetry are you using?
What version of Node are you using?
Node 12
What did you do?
We use OpenTelemetry for tracing and for some requests we see destructuring errors inside
plugin-http
in our error logs.This isn't consistently reproducible but it does happen sometimes. Error trace:
Looks like these occur because
response.socket
can be null:opentelemetry-js/packages/opentelemetry-plugin-http/src/utils.ts
Line 463 in 0cde542
Node docs do mention that:
So maybe that is the source of the problem.
The text was updated successfully, but these errors were encountered: