konsti f70ae72874 Add a `-vv` log level and make `-v` more readable (#2301) ... 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 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.  Best read commit-by-commit.		2024-03-11 08:58:31 +01:00
..
src	Add a `-vv` log level and make `-v` more readable (#2301)	2024-03-11 08:58:31 +01:00
Cargo.toml	Address review feedback on reparse points (#2288)	2024-03-07 16:49:27 -05:00