-
Notifications
You must be signed in to change notification settings - Fork 741
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
Using WithSubscriber with a different registry causes a panic #898
Comments
Oh, I know what's causing this. The tracing/tracing-subscriber/src/registry/stack.rs Lines 64 to 66 in 63c0f31
Unfortunately, this thread -ocal is shared across all instances of This issue hasn't shown up before because I don't think a lot of folks are doing what you're doing using |
I believe this was fixed by #901, and the filtering issues with multiple subscribers that you ran into are tracked elsewhere (and have been fixed in some places). Is that correct? |
Yes 👍 |
Bug Report
Version
Platform
Linux 5.7.12-arch1-1
Description
Started using the
WithSubscriber
trait to optionally use different layers for a specific future. I did this to remove all filters for spans and events inside the future.It mostly appeared to do what I wanted, but I got the following:
Panic backtrace
Here's the code for my layer:
DebugLayer
I then tried a simpler case:
and this gave me a different panic (which killed my process and core dumped), maybe more useful.
Reduced example panic
The text was updated successfully, but these errors were encountered: