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

Warn when RUST_LOG contains a name that isn't a valid path #2038

Closed
jdm opened this issue Mar 21, 2012 · 4 comments
Closed

Warn when RUST_LOG contains a name that isn't a valid path #2038

jdm opened this issue Mar 21, 2012 · 4 comments
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@jdm
Copy link
Contributor

jdm commented Mar 21, 2012

I can't imagine any reason you would actually want a name that isn't a valid logging identifier.

@catamorphism
Copy link
Contributor

Should be fixed as part of implementing #2033.

@bblum
Copy link
Contributor

bblum commented Jun 21, 2013

That bug is now closed, but this is still an issue.

The place to implement this in the old runtime is in update_log_settings. Not sure how the new runtime will deal with it.

@emberian
Copy link
Member

[16:02:15]~/hacking/rust/src/rt> RUST_LOG=foo rustc
warning: got 1 RUST_LOG specs but only matched 0 of them.
You may have mistyped a RUST_LOG spec.
Use RUST_LOG=::help to see the list of crates and modules.

Closing.

@bblum
Copy link
Contributor

bblum commented Aug 11, 2013

Nice!

bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
…1995

Split up `collapsible_if` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `missing-doc` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `use_self` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `if_same_then_else` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `transmute` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `needless_range_loop` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
…phansch

Split up `match_same_arms` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
…lip1995

Split up `non_copy_const` ui test

Part of rust-lang#2038
Maybe there is a better way to avoid duplications of constants.

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
Split up `match` ui test

Part of rust-lang#2038

Also, this decreases the line length limit to 220.

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
…flip1995

Split up `drop_forget_ref` ui test

Part of rust-lang#2038

changelog: none
bors added a commit to rust-lang-ci/rust that referenced this issue May 2, 2020
…1995

Split up `indexing_slicing` ui test

Closes rust-lang#2038

Now all the stderrs are less than 200 lines 🎉

changelog: none
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-runtime Area: std's runtime and "pre-main" init for handling backtraces, unwinds, stack overflows C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

4 participants