-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
fix: otel resiliency #26857
fix: otel resiliency #26857
Conversation
5628e84
to
09ef699
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still in need of tests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
runtime/lib.rs
Outdated
crate::ops::otel::flush(); | ||
std::process::exit(code); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add std::process::exit
to disallowed methods in clippy.toml
files so someone doesn't accidently use it?
Improving the breadth of collected data, and ensuring that the collected data is more likely to be successfully reported.
log
crate in more placeslog
crate to otelprocess::exit
Also adds a more robust testing framework, with a deterministic tracing setting.
Refs: #26852