-
Notifications
You must be signed in to change notification settings - Fork 550
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-express: end() called more than once on async handlers #107
Comments
@vmarchaud can you take a look at this? |
@kellycampbell @dyladan I am facing the same issue. Did you find an alternate solution to avoid this one? |
Sorry for some reason i didn't saw this issue (thanks for the tag on gitter @daudtacto), i will look into this. Note that those are only "warnings", it doesn't impact performance nor can crash your app |
What is the status on this issue? |
@rhummelmose It has been merged but not yet published |
@vmarchaud Cool, I'll try to install from master 👍 |
This has been released in v0.11.0 |
What version of OpenTelemetry are you using?
0.9.0
plugin-express 0.8.0
What version of Node are you using?
12.18.1
What did you do?
Use express.static, or an async handler like a database lookup.
Modified
examples/express/server.js
with the following:What did you expect to see?
No errors in the console.
What did you see instead?
Additional context
Related to open-telemetry/opentelemetry-js#910
One fix that removes the symptoms but I'm not sure if it's the correct solution since it may not trace the work done in the async part of the handler is to add
spanHasEnded = true;
to thesetImmediate
at the end of_applyPatch
:The text was updated successfully, but these errors were encountered: