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
If I use the MISE_TRUSTED_CONFIG_PATHS environment variable, I face the same problem. But if y set this env var to ~/app_0f5a5bcb-cd94-488b-b54e-768cc4f036d7 (just a string, no array), it's working and I have no warning:
But documentation states that a string array is expected and that's what's produced by mise settings set command.
Mise doctor:
version: 2025.1.6 linux-x64 (2025-01-13)
activated: yes
shims_on_path: no
build_info:
Target: x86_64-unknown-linux-gnu
Features: DEFAULT, NATIVE_TLS
Built: Mon, 13 Jan 2025 18:09:04 +0000
Rust Version: rustc 1.84.0 (9fc6b4312 2025-01-07) (built from a source tarball)
Profile: release
shell:
/bin/bash
GNU bash, version 5.2.37(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2022 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
dirs:
cache: ~/.cache/mise
config: ~/.config/mise
data: ~/.local/share/mise
shims: ~/.local/share/mise/shims
state: ~/.local/state/mise
```</div>
The text was updated successfully, but these errors were encountered:
I use this setting for quite a long time and for me this works as expected. If i uncomment the setting i get asked to trust the files as expected.
trusted_config_paths = [
'~/Dev',
]
As for the environment variable MISE_TRUSTED_CONFIG_PATHS the values should be colon separated e.g. export MISE_TRUSTED_CONFIG_PATHS=~/Downloads:~/Dev. The docs currently miss this information for various environment variables which are either comma or colon separated. Something to follow up on as well.
Discussed in #4212
Originally posted by davlgd January 24, 2025
My application is in
~/app_0f5a5bcb-cd94-488b-b54e-768cc4f036d7
which is untrusted.To trust it, I add a setting which is not working:
If I use the
MISE_TRUSTED_CONFIG_PATHS
environment variable, I face the same problem. But if y set this env var to~/app_0f5a5bcb-cd94-488b-b54e-768cc4f036d7
(just a string, no array), it's working and I have no warning:But documentation states that a string array is expected and that's what's produced by
mise settings set
command.Mise doctor:
The text was updated successfully, but these errors were encountered: