-
Notifications
You must be signed in to change notification settings - Fork 19
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
tracing core module and node 0.11.15 #12
Comments
Oh, yeah, that was supposed to happen eventually. @trevnorris what is the recommended alternative to the |
Nothing right now. Currently there is an undocumented way to tap into |
@trevnorris Thanks for clarifying, I will try migrating to that API. |
@mpal9000 I'm working on it. But unfortunately there is a few bugs in the new |
All right, thank you! |
@mpal9000 node 0.11.15, 0.11.16 and iojs should now be supported. However it uses some really dirty hacks so I can't promise anything, but we will just have to take those issues as they appear. Node 0.11.14 is still supported using the old approach, so you can downgrade to that if you hit any major issues. EDIT: there is also some performance hit. The benchmark went from 7x slower to 11x slower than the baseline (without trace). However with the recent upgrade to stack-chain 1.3.1 it pretty much cancels out. |
I'll let you know if I have any issues, thanks! |
Hi, the "tracing" core module has been removed from node v0.11.15
The text was updated successfully, but these errors were encountered: