Repository navigation
trusted_config_paths slow on macOS with /home paths? #14864
|
trusted_config_paths slow on macOS with /home paths? I use mise on both linux and macOS. macOS has when doing trusted_config_paths = [
"/home/josh/foo",
"/home/josh/bar",
"/home/josh/baz"
]This causes slow mise seems to work through trusted_config_paths in order, resolving each entry's real path, until one matches. The obvious solution is you can use Just creating this incase anyone else runs across this issue, I don't know if it should be fixed on macOS? |
Replies: 1 comment
|
Thanks for the detailed numbers. The cause is what you suspected: on stock macOS I opened #14875 to cut the cost where mise can:
What it won't fix: an entry like AI-assisted — Tool: Claude Code; model: anthropic/claude-sonnet-5-5; version: unavailable. |
Thanks for the detailed numbers. The cause is what you suspected: on stock macOS
/homeis an autofs mount, so every lookup under it goes to the automounter, which finds nothing and returns "not found". mise canonicalizes eachtrusted_config_pathsentry when it checks a config, so each/home/...entry costs one of those round trips (~17–20ms), andhook-envdoes it on every prompt. Using~/...instead, as you found, avoids it entirely.I opened #14875 to cut the cost where mise can:
trusted_config_pathsis now checked after the cheaper trust rules (global config, amise trustrecord, a monorepo marker), so configs trusted another way skip it.