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 a -vv
log level and make -v
more readable
#2301
Conversation
Without reading through everything here.. my initial thoughts about logging are:
|
My thought was to not have too many flags but have users quickly switch to |
I don't think |
Where would you source those messages, from what we currently show as reporter spinner status message? |
I'm not sure! I'm not super familiar with our logging setup. I presume we'd use |
The hierarchical layer is verbose and hard to follow, so it's moved to the `-vv` extra verbose setting, while `-v` works like `RUST_LOG=uv=debug`. For installing jupyter with a warm cache: * Default: https://gist.github.com/konstin/4de6e466127311c5a5fc2f99c56a8e11 * `-v`: https://gist.github.com/konstin/e7bafe0ec7d07e47ba98a3865ae2ef3e * `-vv`: https://gist.github.com/konstin/3ee1aaff37f91cceb6275dd5525f180e Ideally, we would have `-v`, `-vv` and `-vvv`, but we're lacking the the `info!` layer for `-v`, so there's only two layers for now. The `tracing_subcriber` formatter always print the current span, so i replaced it with a custom formatter. ![image](https://github.com/astral-sh/uv/assets/6826232/75f5cfd1-da7b-432e-b090-2f3916930dd1)
I agree, but we're currently lacking an |
-vv
log level and make -v
more readable
Behind error messages, the debug log is the second most important resource to finding out what and why went wrong when there was a problem with uv. It is important to see which paths it has found and how the decisions in the resolver were made. I'm trying to improve the experience interacting with the debug log.
The hierarchical layer is verbose and hard to follow, so it's moved to the
-vv
extra verbose setting, while-v
works likeRUST_LOG=uv=debug
.For installing jupyter with a warm cache:
-v
: https://gist.github.com/konstin/e7bafe0ec7d07e47ba98a3865ae2ef3e-vv
: https://gist.github.com/konstin/3ee1aaff37f91cceb6275dd5525f180eIdeally, we would have
-v
,-vv
and-vvv
, but we're lacking the theinfo!
layer for-v
, so there's only two layers for now.The
tracing_subcriber
formatter always print the current span, so i replaced it with a custom formatter.Best read commit-by-commit.