-
Notifications
You must be signed in to change notification settings - Fork 893
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
feat(cli)!: set log level to INFO
/DEBUG
on --quiet
/--verbose
if RUSTUP_LOG
is unset
#3987
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
from
August 10, 2024 12:44
ce06464
to
9a89b21
Compare
rami3l
commented
Aug 10, 2024
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
from
August 10, 2024 13:02
9a89b21
to
4dd99b0
Compare
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
2 times, most recently
from
August 11, 2024 03:28
1eb60b5
to
349feec
Compare
rami3l
changed the title
feat(cli)!: set log level to
feat(cli)!: set log level to Aug 11, 2024
DEBUG
on --verbose
if RUSTUP_LOG
is unsetINFO
/DEBUG
on --quiet
/--verbose
if RUSTUP_LOG
is unset
djc
reviewed
Aug 19, 2024
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
from
August 22, 2024 07:01
349feec
to
f1d1fdb
Compare
5 tasks
djc
approved these changes
Sep 4, 2024
Sorry for the slow feedback, this is looking good! |
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
from
September 4, 2024 09:24
f1d1fdb
to
915a84e
Compare
…`--verbose` if `RUSTUP_LOG` is unset
rami3l
force-pushed
the
feat/more-consistent-verbose
branch
from
September 4, 2024 09:27
915a84e
to
b15e0a0
Compare
3 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current setting,
debug!()
lines are not printed out even if I useRUSTUP_LOG=rustup=DEBUG
. This logic used to make sense when we didn't have support for directives, but now it feels a bit awkward.As a solution, I decided to follow the basic idea of #3911:
RUSTUP_LOG
decides ultimately when it's present.RUSTUP_LOG
is unset,--quiet
or--verbose
gets to decide the log verbosity.Overall, now
--quiet
and--verbose
behave more like what would be expected from general CLI applications.This applies to both
rustup-mode
(i.e.rustup
) andsetup-mode
(i.e.rustup-init
).