-
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
feat: allow manual instrumentation when instrument is set to false #1114
feat: allow manual instrumentation when instrument is set to false #1114
Conversation
db941e4
to
34130a2
Compare
We should probably put this in v3.0.0 as it could be considered a breaking change 🤔 |
8599942
to
9667564
Compare
True. Marking as breaking change. |
e728708
to
2a82b8b
Compare
d82d594
to
ac0be47
Compare
Jenkins run the tests please |
I'm able to reproduce the Travis failure locally. The issue is that the CPU just starts spinning forever during the When it occurs, the process hangs so badly that you need to run a |
Ok, I can reproduce it again - but not every time. Turns out the error doesn't always happen, so sometimes you need to run the test command a few times before it occurs. So I usually run it like this:
I made a core dump while the script was stuck in the infinite loop and discovered that it was related to async hooks. When disabling async hooks in the |
I think I narrowed it down to multiple async hooks being enabled during the Working on a fix... |
I've fixed the CI issue in #1373. Once that's merged, |
9efebeb
to
582d18a
Compare
I think you accidentally force pushed a version that removed my last commit. I assume that was just because you rebased with I'll force push a new version with the extra commits. Hope you don't mind 🙂 |
582d18a
to
3b5e043
Compare
jenkins run the tests please |
Ah, sorry about that. I missed your commits. 😅 |
jenkins run the tests please |
Fixes #858
Checklist