-
Notifications
You must be signed in to change notification settings - Fork 134
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
Clear thread local variables when forked #1214
base: main
Are you sure you want to change the base?
Conversation
💔 Tests Failed
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures> Show only the first 10 test failures
|
Wow, what a find! 👏 |
@estolfo still no luck for us. We're still seeing all those random spans getting collected on that one worker. |
🌐 Coverage report
|
@estolfo we're still using this branch and I was wondering if this is going to get merged or what exactly is happening here. Wanted to get us back on the main version. |
Hi @jclusso I made these changes hoping they would fix the issues you were seeing but when we tested, they didn't. So I am hesitant to merge these changes without a specific reason, though in theory, they make sense. @jaggederest is working on the agent now so I'll ask him to review these changes and help decide if they should be merged. |
Going to try running the main branch. We’ve been sitting on your fork. |
Thread local variables are copied over when a process is forked so we should clear the MongoSpy thread locals when forked.