jdx/mise · error

No current versions found after resolving toolset

Error message

No current versions found after resolving toolset

What it means

Invariant failure during tool stub execution (execute_with_tool_request): after resolving and building the toolset, no current versions remain (the toolset's version list is empty), so there is nothing to execute. Fires when resolution filters out all versions (e.g. bad lock data, platform mismatch) yet the code path expects at least one.

Source

Thrown at src/cli/tool_stub.rs:547

    // Inject lock data from stub into tool versions
    // The toolset contains only the single tool from this stub, so apply to all versions
    if let Some(lock) = &stub.lock {
        for (_ba, tvl) in toolset.versions.iter_mut() {
            for tv in &mut tvl.versions {
                for (platform_key, lock_platform) in &lock.platforms {
                    let pi = PlatformInfo {
                        url: lock_platform.url.clone(),
                        checksum: lock_platform.checksum.clone(),
                        ..Default::default()
                    };
                    tv.lock_platforms.insert(platform_key.clone(), pi);
                }
            }
        }
    }

    // Ensure we have current versions after resolving
    ensure!(
        !toolset.list_current_versions().is_empty(),
        "No current versions found after resolving toolset"
    );

    // Install the tool if it's missing
    let install_opts = InstallOptions {
        force: false,
        jobs: None,
        raw: false,
        missing_args_only: false,
        resolve_options: Default::default(),
        ..Default::default()
    };

    let (_, missing) = toolset
        .install_missing_versions(config, &install_opts)
        .await?;
    toolset.notify_missing_versions(missing);

View on GitHub (pinned to afd2eddd3a)

Solutions

  1. Check the stub's lock data and the requested version against the tool's installed versions
  2. Re-resolve the toolset to see why versions were filtered out
  3. Reinstall the tool or fix lockfile platform entries, then retry the stub
Defensive patterns

Strategy: fallback

When it happens

Trigger: Thrown at src/cli/tool_stub.rs:547 when the library encounters an invalid state.

Common situations: See trigger scenarios.


AI-assisted analysis of jdx/mise@afd2eddd3a (2026-09-09). Data as JSON: /api/errors/f89f944c1f6d5364. Report an issue: GitHub.