Skip to content
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

refactor: allow resolve span to be disabled #153

Merged
merged 1 commit into from
Oct 8, 2024

Conversation

seanmonstar
Copy link
Member

Because of what's noted in seanmonstar/reqwest#2435

@GeorgeHahn
Copy link

This also causes a panic when tracing_subscriber::Registry is in use (tokio-rs/tracing#1656). I was able to work around it by downgrading to hyper-util 0.1.7.

@seanmonstar
Copy link
Member Author

@GeorgeHahn the change in this PR causes a panic?

@GeorgeHahn
Copy link

Sorry, I should have worded that differently. This PR will fix a panic. The or_current call brings the current span into the spawned task and tracing will panic if that span has been closed by the time the task completes. This panic is a sharp edge in tracing's Registry.

@seanmonstar seanmonstar merged commit aa90ce5 into master Oct 8, 2024
16 checks passed
@seanmonstar seanmonstar deleted the dns-span-not-or-current branch October 8, 2024 18:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants