You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mise error messages are verbose because of the facility used to print them:
$ mise self-updateError: 0: mise is installed via a package manager, cannot updateLocation: src/cli/self_update.rs:39Version: 2024.8.4 macos-arm64 (2024-08-02)Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.Run with RUST_BACKTRACE=full to include source snippets.
I understand that it's nice to use the same output facility for all error messages, but in case of "simple" messages like this, I would expect to see something more like:
$ mise self-updatemise is installed via a package manager, cannot update
This is especially noisy because it happens on command-line rendering if there is an untrusted .mise.toml file:
Error: 0: Config file is not trusted. Trust it with `mise trust`.Location: src/config/config_file/mod.rs:214Version: 2024.8.4 macos-arm64 (2024-08-02)Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.Run with RUST_BACKTRACE=full to include source snippets.
$ |
Here, this message is both too verbose (I don't need location or version or the backtrace message) and insufficiently verbose (which config file is untrusted?; it could be ~/.config/mise/config.toml if I edited it recently). I would expect to see, instead:
Error: Config file `path/to/file/.mise.toml` is not trusted.Trust it with `mise trust`.
$ |
I think there are errors that could happen where the location and version might be useful — but for the most part, I don't think that information is helpful to the casual user of mise.
The text was updated successfully, but these errors were encountered:
Mise error messages are verbose because of the facility used to print them:
I understand that it's nice to use the same output facility for all error messages, but in case of "simple" messages like this, I would expect to see something more like:
This is especially noisy because it happens on command-line rendering if there is an untrusted
.mise.toml
file:Here, this message is both too verbose (I don't need location or version or the backtrace message) and insufficiently verbose (which config file is untrusted?; it could be
~/.config/mise/config.toml
if I edited it recently). I would expect to see, instead:I think there are errors that could happen where the location and version might be useful — but for the most part, I don't think that information is helpful to the casual user of
mise
.The text was updated successfully, but these errors were encountered: