Custom mise init task stopped working suddenly in v2024.12.15 with spurious "No such file or directory error" #4400

gebailey · 2025-02-14T18:32:56Z

gebailey
Feb 14, 2025

Our team uses mise in various GitHub actions workflows. We'd like to stay current with recent mise versions. Those workflows fail when mise v2024.12.15 is used, but succeed when v2024.12.14 is used. We're attempting to perform a mise install -y step in a file-based task. I can reproduce this in a pristine environment (a machine with no mise, python, node, etc.)

mise.toml file:

[tools]
node = "22"
"npm:aws-cdk" = "latest"
"npm:prettier" = "latest"
python = "3.12"
usage = "latest"
uv = "latest"

[env]
# relative to this file's directory
_.python.venv = ".venv" # Add python virtual environment to PATH.

[tasks.e2e]
description = 'Run end-to-end tests.'
run = "echo 'Not implemented.'"

[settings]

[settings.python]
compile = false

[settings.node]
compile = false

mise/tasks/init:

#!/usr/bin/bash
# mise description="Run tool setup and install packages."

set -e # Exit on error

# other setup is done here...

mise install -y

SUCCESS using mise version v2024.12.14:

rm -rf ~/.cache ~/.local ~/.npm
curl https://mise.jdx.dev/install.sh | MISE_VERSION=v2024.12.14 sh
eval "$(mise activate --shims)"
mise trust
mise run init

FAILURE using mise version v2024.12.15:

rm -rf ~/.cache ~/.local ~/.npm
curl https://mise.jdx.dev/install.sh | MISE_VERSION=v2024.12.15 sh
eval "$(mise activate --shims)"
mise trust
mise run init

yields the following error output:

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  9554  100  9554    0     0  25993      0 --:--:-- --:--:-- --:--:-- 26032
mise: installing mise...
######################################################################## 100.0%
mise: installed successfully to /home/vagrant/.local/bin/mise
mise: run the following to activate mise in your shell:
echo "eval \"\$(/home/vagrant/.local/bin/mise activate bash)\"" >> ~/.bashrc

mise: run `mise doctor` to verify this is setup correctly
mise trusted /home/vagrant/mise-bug
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  rendering task: 
   0: [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
   1: [~/mise-bug/mise.toml] npm:aws-cdk@latest: No such file or directory (os error 2)
   2: error resolving versions

Location:
   src/toolset/mod.rs:158

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  loading tasks in ~/mise-bug/mise/tasks: [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
mise ERROR no task init found
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

subsequent commands give errors:

vagrant@ubuntu-jammy:~/mise-bug$ mise list
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise ERROR [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
mise ERROR [~/mise-bug/mise.toml] npm:aws-cdk@latest: No such file or directory (os error 2)
mise ERROR error resolving versions
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

mise doctor output:

vagrant@ubuntu-jammy:~/mise-bug$ mise doctor
version: 2024.12.15 linux-x64 (0d37f33 2024-12-19)
activated: no
shims_on_path: yes

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Thu, 19 Dec 2024 18:51:16 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  /bin/bash
  GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
  Copyright (C) 2020 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

config_files:
  ~/mise-bug/mise.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
mise WARN  failed to resolve toolset: [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)

toolset:
  aqua:astral-sh/[email protected]  (missing)
  core:[email protected]     (missing)
  core:[email protected]    (missing)
  ubi:jdx/[email protected]   (missing)
mise WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv

path:
  ~/.local/bin
  /usr/local/sbin
  /usr/local/bin
  /usr/sbin
  /usr/bin
  /sbin
  /bin
  /usr/games
  /usr/local/games
  /snap/bin

env_vars:
  (none)

settings:
  node.compile    false ~/mise-bug/mise.toml
  python.compile  false ~/mise-bug/mise.toml
mise WARN  mise version 2025.2.3 available
mise WARN  To update, run mise self-update

1 problem found:

1. new mise version 2025.2.3 available, currently on 2024.12.15

If I perform the same mise install -y here, it succeeds. How can I use mise install within a file-based task? I couldn't tell from the v2024.12.15 changelog what might have affected this behavior.

jdx · 2025-02-14T18:37:14Z

jdx
Feb 14, 2025
Maintainer

if you enable debug/trace you should have a better idea of what is happening

0 replies

gebailey · 2025-02-14T18:46:16Z

gebailey
Feb 14, 2025
Author

Running that last failure step with (I think?) debug/trace:

$ MISE_VERBOSE=1 RUST_BACKTRACE=1 mise run init
DEBUG mkdirp: "/home/vagrant/.cache/mise/.auto_prune"
DEBUG pruning old cache files, this behavior can be modified with the MISE_CACHE_PRUNE_AGE setting
DEBUG ARGS: mise run init
DEBUG EnvResults
DEBUG config: ~/mise-bug/mise.toml
DEBUG $ npm view aws-cdk dist-tags --json
DEBUG EnvResults
WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
DEBUG EnvResults
DEBUG $ npm view prettier dist-tags --json
WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
DEBUG EnvResults
WARN  rendering task: 
   0: [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
   1: [~/mise-bug/mise.toml] npm:aws-cdk@latest: No such file or directory (os error 2)
   2: error resolving versions

Location:
   src/toolset/mod.rs:158

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 2 frames hidden ⋮                               
   3: mise::toolset::Toolset::resolve::h339fca41a1f18b31
      at <unknown source file>:<unknown line>
   4: once_cell::imp::OnceCell<T>::initialize::{{closure}}::h4625f42a02ead196
      at <unknown source file>:<unknown line>
   5: once_cell::imp::initialize_or_wait::h9f540d28d5d27035
      at <unknown source file>:<unknown line>
   6: once_cell::imp::OnceCell<T>::initialize::ha98fe687512d236a
      at <unknown source file>:<unknown line>
   7: mise::task::Task::tera_ctx::hb0df1e4d95320ec0
      at <unknown source file>:<unknown line>
   8: mise::task::Task::render::h6a6abf3dd9e41efa
      at <unknown source file>:<unknown line>
   9: alloc::vec::in_place_collect::<impl alloc::vec::spec_from_iter::SpecFromIter<T,I> for alloc::vec::Vec<T>>::from_iter::h48e2cc7a1d16f582
      at <unknown source file>:<unknown line>
  10: rayon::iter::plumbing::bridge_producer_consumer::helper::h86488347c9a2d5af
      at <unknown source file>:<unknown line>
  11: mise::config::Config::load_tasks_in_dir::hca300b02a8c821dd
      at <unknown source file>:<unknown line>
  12: rayon::iter::plumbing::bridge_producer_consumer::helper::hfd314a5fff5594e9
      at <unknown source file>:<unknown line>
  13: rayon_core::join::join_context::{{closure}}::hb6186dc640dcbb3f
      at <unknown source file>:<unknown line>
  14: rayon::iter::plumbing::bridge_producer_consumer::helper::hfd314a5fff5594e9
      at <unknown source file>:<unknown line>
  15: rayon_core::join::join_context::{{closure}}::hb6186dc640dcbb3f
      at <unknown source file>:<unknown line>
  16: rayon::iter::plumbing::bridge_producer_consumer::helper::hfd314a5fff5594e9
      at <unknown source file>:<unknown line>
  17: <rayon_core::job::HeapJob<BODY> as rayon_core::job::Job>::execute::h663c3b9d51edb9db
      at <unknown source file>:<unknown line>
  18: rayon_core::registry::WorkerThread::wait_until_cold::h6f2954c23db70d40
      at <unknown source file>:<unknown line>
  19: rayon_core::scope::ScopeBase::complete::h33d08d85a6c1f68e
      at <unknown source file>:<unknown line>
  20: rayon_core::scope::scope::{{closure}}::h2d21e02e3f0d622f
      at <unknown source file>:<unknown line>
  21: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute::h1dc6b7c6d8c57b1d
      at <unknown source file>:<unknown line>
  22: rayon_core::registry::WorkerThread::wait_until_cold::h6f2954c23db70d40
      at <unknown source file>:<unknown line>
  23: std::sys::backtrace::__rust_begin_short_backtrace::ha1ffd6eeb41e89a8
      at <unknown source file>:<unknown line>
  24: core::ops::function::FnOnce::call_once{{vtable.shim}}::h6a0fb7f8f09cb135
      at <unknown source file>:<unknown line>
  25: std::sys::pal::unix::thread::Thread::new::thread_start::hcc78f3943333fa94
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
DEBUG $ npm view aws-cdk dist-tags --json
WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
DEBUG EnvResults
DEBUG $ npm view prettier dist-tags --json
WARN  no venv found at: ~/mise-bug/.venv
To create a virtualenv manually, run:
python -m venv ~/mise-bug/.venv
DEBUG EnvResults
WARN  loading tasks in ~/mise-bug/mise/tasks: [~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
Error: 
   0: no task init found

Location:
   src/cli/run.rs:909

Version:
   2024.12.15 linux-x64 (0d37f33 2024-12-19)

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 2 frames hidden ⋮                               
   3: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once::h308fc2ac4af54c41
      at <unknown source file>:<unknown line>
   4: <core::iter::adapters::GenericShunt<I,R> as core::iter::traits::iterator::Iterator>::next::h35c3035c38fcc752
      at <unknown source file>:<unknown line>
   5: core::iter::adapters::try_process::hd0c55896ae9b8719
      at <unknown source file>:<unknown line>
   6: mise::cli::run::Run::run::h6553e0ed638e0977
      at <unknown source file>:<unknown line>
   7: mise::cli::Commands::run::ha8719e645abca1cd
      at <unknown source file>:<unknown line>
   8: mise::cli::Cli::run::h98a2245c36fbee55
      at <unknown source file>:<unknown line>
   9: mise::main::hf68ac3b3db0b642d
      at <unknown source file>:<unknown line>
  10: std::sys::backtrace::__rust_begin_short_backtrace::h603fef5a2aad7fd4
      at <unknown source file>:<unknown line>
  11: main<unknown>
      at <unknown source file>:<unknown line>
  12: __libc_start_main<unknown>
      at <unknown source file>:<unknown line>
  13: _start<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.

1 reply

gebailey Feb 14, 2025
Author

WARN loading tasks in ~~/mise-bug/mise/tasks: [~~/mise-bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
Error:
0: no task init found

Seems like there's some issue parsing the "npm:prettier" = "latest" entry in mise.toml (looking for a filename?) but I don't understand the backtrace.

gebailey · 2025-02-25T16:48:30Z

gebailey
Feb 25, 2025
Author

Simpler reproduction scenario:

mise.toml

[tools]
node = "22"
uv = "latest"
"npm:prettier" = "latest"

[tasks.e2e]
description = 'Run end-to-end tests.'
run = "echo 'Not implemented.'"

FAILING SCENARIO

[vagrant@vbox bug]$ rm -rf ~/.cache ~/.local ~/.npm

[vagrant@vbox bug]$ curl --silent https://mise.jdx.dev/install.sh | MISE_VERSION=v2025.2.8 sh
mise: installing mise...
######################################################################## 100.0%
mise: installed successfully to /home/vagrant/.local/bin/mise
mise: run the following to activate mise in your shell:
echo "eval \"\$(/home/vagrant/.local/bin/mise activate bash)\"" >> ~/.bashrc

mise: run `mise doctor` to verify this is setup correctly

[vagrant@vbox bug]$ mise trust
mise trusted /home/vagrant/bug

[vagrant@vbox bug]$ mise doctor
version: 2025.2.8 linux-x64 (2025-02-25)
activated: no
shims_on_path: no

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL, SELF_UPDATE
  Built: Tue, 25 Feb 2025 02:12:16 +0000
  Rust Version: rustc 1.84.1 (e71f9a9a9 2025-01-27)
  Profile: release

shell:
  /bin/bash
  GNU bash, version 5.2.32(1)-release (x86_64-redhat-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

config_files:
  ~/bug/mise.toml

ignored_config_files: (none)

backends:
  aqua
  asdf
  cargo
  core
  dotnet
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
mise WARN  failed to resolve toolset: [~/bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)

toolset:
  aqua:astral-sh/[email protected]  (missing)
  core:[email protected]     (missing)

path:
  ~/.local/bin
  ~/bin
  /usr/local/bin
  /usr/bin
  /usr/local/sbin
  /usr/sbin

env_vars:
  (none)

settings:

1 problem found:

1. mise is not activated, run mise help activate or
   read documentation at https://mise.jdx.dev for activation instructions.
   Alternatively, add the shims directory ~/.local/share/mise/shims to PATH.
   Using the shims directory is preferred for non-interactive setups.

[vagrant@vbox bug]$ mise ls
mise ERROR [~/bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
mise ERROR error resolving versions
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

[vagrant@vbox bug]$ mise tasks
mise ERROR [~/bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
mise ERROR error resolving versions
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

If I try the above steps with mise version v2024.12.14, at least the tasks listing is available. I get:

[vagrant@vbox bug]$ rm -rf ~/.cache ~/.local ~/.npm

[vagrant@vbox bug]$ curl --silent https://mise.jdx.dev/install.sh | MISE_VERSION=v2024.12.14 sh
mise: installing mise...
######################################################################## 100.0%
mise: installed successfully to /home/vagrant/.local/bin/mise
mise: run the following to activate mise in your shell:
echo "eval \"\$(/home/vagrant/.local/bin/mise activate bash)\"" >> ~/.bashrc

mise: run `mise doctor` to verify this is setup correctly

[vagrant@vbox bug]$ mise trust
mise trusted /home/vagrant/bug

[vagrant@vbox bug]$ mise doctor
version: 2024.12.14 linux-x64 (ac3079c 2024-12-18)
activated: no
shims_on_path: no

build_info:
  Target: x86_64-unknown-linux-gnu
  Features: DEFAULT, NATIVE_TLS, OPENSSL
  Built: Wed, 18 Dec 2024 18:58:12 +0000
  Rust Version: rustc 1.83.0 (90b35a623 2024-11-26)
  Profile: release

shell:
  /bin/bash
  GNU bash, version 5.2.32(1)-release (x86_64-redhat-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

config_files:
  ~/bug/mise.toml

backends:
  aqua
  asdf
  cargo
  core
  gem
  go
  npm
  pipx
  spm
  ubi
  vfox

plugins:
mise WARN  failed to resolve toolset: [~/bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)

toolset:
  aqua:astral-sh/[email protected]  (missing)
  core:[email protected]     (missing)

path:
  ~/.local/bin
  ~/bin
  /usr/local/bin
  /usr/bin
  /usr/local/sbin
  /usr/sbin

env_vars:
  (none)

settings:
mise WARN  mise version 2025.2.8 available
mise WARN  To update, run mise self-update

2 problems found:

1. mise is not activated, run mise help activate or
   read documentation at https://mise.jdx.dev for activation instructions.
   Alternatively, add the shims directory ~/.local/share/mise/shims to PATH.
   Using the shims directory is preferred for non-interactive setups.

2. new mise version 2025.2.8 available, currently on 2024.12.14

[vagrant@vbox bug]$ mise ls
mise ERROR [~/bug/mise.toml] npm:prettier@latest: No such file or directory (os error 2)
mise ERROR error resolving versions
mise ERROR Run with --verbose or MISE_VERBOSE=1 for more information

[vagrant@vbox bug]$ mise tasks
Name  Description           
e2e   Run end-to-end tests.

In both cases, the npm:prettier@latest: No such file or directory (os error 2) warning is strange -- as if npm:prettier@latest is referenced as a file. (If I remove npm:prettier from the [tools] section of mise.toml, I don't see this behavior).

0 replies

gebailey · 2025-02-25T17:18:10Z

gebailey
Feb 25, 2025
Author

This error condition also does not occur if npm is available on a system path. The error seems to occur only in a clean environment with no npm tool installed.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Custom mise init task stopped working suddenly in v2024.12.15 with spurious "No such file or directory error" #4400

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 4 comments 1 reply

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

Select a reply

Custom mise init task stopped working suddenly in v2024.12.15 with spurious "No such file or directory error" #4400

gebailey Feb 14, 2025

Replies: 4 comments · 1 reply

jdx Feb 14, 2025 Maintainer

gebailey Feb 14, 2025 Author

gebailey Feb 14, 2025 Author

gebailey Feb 25, 2025 Author

gebailey Feb 25, 2025 Author

gebailey
Feb 14, 2025

Replies: 4 comments 1 reply

jdx
Feb 14, 2025
Maintainer

gebailey
Feb 14, 2025
Author

gebailey Feb 14, 2025
Author

gebailey
Feb 25, 2025
Author

gebailey
Feb 25, 2025
Author