-
Notifications
You must be signed in to change notification settings - Fork 27
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
Add tracing for extra structured debug logging #129
Conversation
Codecov Report
@@ Coverage Diff @@
## main #129 +/- ##
===========================================
- Coverage 55.92% 44.60% -11.33%
===========================================
Files 13 12 -1
Lines 751 639 -112
===========================================
- Hits 420 285 -135
- Misses 331 354 +23
Continue to review full report at Codecov.
|
bors r+ |
bors r- |
Canceled. |
…sers Adds logic to initialize tracing. The tracing information is logged to a file, which will be rotated daily. The events logged using tracing may be more detailed, or simply different from the output we would like to show users. Tracing may be disabled by running cargo-msrv with the `--no-log` flag. In that case, not even a log file will be created, which may be useful if the log file location (which is currently not configurable) is inaccessible. For the implementation it is important that we always collect the guards of the non-blocking tracing appender(s), since they will only live as long as the lifetime of the worker guard. If we don't do this, the guards would be dropped after the scope of `if !config.no_tracing() { ... }` ended, and as a result, anything logged in `init_and_run` would not be logged.
bors r+ |
No description provided.