-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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: migrate to tracing
#12458
refactor: migrate to tracing
#12458
Conversation
r? @ehuss (rustbot has picked a reviewer for you, use r? to override) |
Compatibility only matters if we intend people to parse it which I don't think we do. The only other issue is usability which it is probably good enough |
I'd like to call out the other change. By default |
@bors r+ |
💥 Test timed out |
Timed out again… @bors retry |
☀️ Test successful - checks-actions |
Update cargo 21 commits in d78bbf4bde3c6b95caca7512f537c6f9721426ff..7e9de3f4ec3708f500bec142317895b96131e47c 2023-08-03 12:58:25 +0000 to 2023-08-13 00:47:32 +0000 - feat: remove `--keep-going` from `cargo test/bench` (rust-lang/cargo#12478) - chore: window-sys should be a platform-specific dependency (rust-lang/cargo#12483) - docs: make the env var source of rerun-if-env-changed clearer (rust-lang/cargo#12482) - doc: note the backward compatible `.cargo/credential` file exists (rust-lang/cargo#12479) - Fix elided lifetime in associated const (rust-lang/cargo#12475) - prompt the use of `--nocapture` flag if `cargo test` process is terminated via a signal. (rust-lang/cargo#12463) - cargo-credential: reset stdin & stdout to the Console (rust-lang/cargo#12469) - Fix cargo remove incorrectly removing used patches (rust-lang/cargo#12454) - chore(gh): Expand update window (rust-lang/cargo#12466) - Fix panic when enabling http.debug for certain strings (rust-lang/cargo#12468) - fix(cli): Make `--help` easier to browse (rust-lang/cargo#11905) - fix: preserve jobserver file descriptors on rustc invocation to get `TargetInfo` (rust-lang/cargo#12447) - refactor: migrate to `tracing` (rust-lang/cargo#12458) - docs: add example for cargo-credential (rust-lang/cargo#12461) - Bail out an error when using cargo:: in custom build script (rust-lang/cargo#12332) - Fix printing multiple warning messages for unused fields in [registries] table (rust-lang/cargo#12439) - Update windows dependencies (rust-lang/cargo#12453) - Rustfmt a let-else statement (rust-lang/cargo#12451) - Add allow(internal_features) (rust-lang/cargo#12450) - Update pretty_env_logger to 0.5 (rust-lang/cargo#12445) - Remove build metadata from libgit2-sys dependency (rust-lang/cargo#12444) r? `@ghost`
What does this PR try to resolve?
The migrates
CARGO_LOG
logging fromlog
totracing
.tracing
is already widely used among the ecosystem and rustc adopted it for a while. We've chatted about this a while back in the weekly meeting.Last week in the office hour, epage, Muscraft, and arlosi have no objection to this when I mentioned this upcoming PR. ehuss seems to looking forward to the migration #12445 (comment). Hence posted this pull request.
How should we test and review this PR?
By commits. And please check if
CARGO_LOG
works for you.Largely, a search & replace worked just fine. Only in
util/network/http.rs
I did a manual fix.The format is also a bit different. Should we make it compatible? (I don't want to though)
By default
log
enables all levels, whereas the built-infmt
subscriber in tracing-subscriber enables up toINFO
only. Is that a thing we need to consider? I do feel like INFO is a better default.Additional information
Last year during 1.63.0 release cargo only had ~180 deps, but today it doubles the number to ~337 🥲.