Repository navigation
warning on missing lazy tools #13166
|
In our root [tools]
"java" = { version = "corretto-21" }
# lazy tools
"agent-browser" = { version = "latest", lazy = true, lazy_bins = [
"agent-browser",
] }
"fd" = { version = "latest", lazy = true }
"fzf" = { version = "latest", lazy = true }
"gh" = { version = "latest", lazy = true }
"jq" = { version = "latest", lazy = true }Users never invoked a script or task that uses that lazy tool, yet every time they change directories or install the dependencies, mise warns that those lazy tools are missing. Is that expected? The only guess I have is that some tasks use scripts that rely on those lazy tools, but as I said, nobody invoked those tasks and encountered the warning. |
Replies: 1 comment
|
Thanks for the report—this is not expected. The warnings are coming from the directory-entry missing-tool notifier, not from mise discovering or executing task scripts. A bare I opened #13169 to exclude lazy declarations from missing-tool status messages while preserving warnings for ordinary missing tools. Lazy tools will still install normally when their command is first invoked. AI-assisted — Tool: Codex; model: openai/gpt-5; version: unavailable. |
Thanks for the report—this is not expected. The warnings are coming from the directory-entry missing-tool notifier, not from mise discovering or executing task scripts.
A bare
mise installcorrectly leaveslazy = truetools uninstalled, but the shared notifier was still treating those intentionally absent tools as missing. With the defaultif_other_versions_installedpolicy, this is especially visible when an older version of alatesttool is already installed.I opened #13169 to exclude lazy declarations from missing-tool status messages while preserving warnings for ordinary missing tools. Lazy tools will still install normally when their command is first invoked.
AI-assisted — Tool: Co…