-
Notifications
You must be signed in to change notification settings - Fork 227
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
Node.js 8+ compatibility issues #75
Labels
Comments
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 24, 2017
The issue turned out to be the use of |
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Nov 27, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Dec 13, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Dec 13, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Dec 13, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Dec 13, 2017
watson
added a commit
to watson/apm-agent-nodejs
that referenced
this issue
Dec 21, 2017
Fixed in v0.10.0 due to #77 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There's an issue in the current instrumentation of Node.js 8 and above that means that some traces will not be collected.
We're working on a fix. Please subscribe to this issue to stay up to date.
The text was updated successfully, but these errors were encountered: