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

Tracing initialization improvements #1244

Merged
merged 4 commits into from
Mar 1, 2024
Merged

Conversation

svix-jplatte
Copy link
Member

Previously, it was possible that tests would overwrite each other's intended logging configuration.

@svix-jplatte svix-jplatte requested a review from a team as a code owner March 1, 2024 11:22
@svix-james
Copy link
Contributor

This is a great change. I don't know whether it will actually fix our problems related to testing, though. For example, when I've tried to instrument tests to reconfigure the tracer per test, I've had no luck. If I make a direct call to opentelemetry::global::shutdown_tracer_provider() at the beginning of a test, the call will just hang indefinitely, which I believe is related to this issue: open-telemetry/opentelemetry-rust#868

@svix-jplatte svix-jplatte merged commit af07e7e into main Mar 1, 2024
6 checks passed
@svix-jplatte svix-jplatte deleted the jplatte/tracing-setup branch March 1, 2024 23:08
svix-jplatte added a commit that referenced this pull request Mar 14, 2024
Since #1244, we were no longer installing a global tracing subscriber
that would print logs from (failing) tests. With this, we do again.

First two commits are drive-by improvements in response to local
warnings from my nightly toolchain about redundant imports.
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