jdx/mise · error

not set up

Error message

not set up

What it means

State precondition in onboard run(): the machine is not yet set up for history synchronization (no tracked state/connection for onboarding to act on), detected while running the dry-run preview of sync and apply. The onboarding flow requires an initialized setup before proceeding.

Source

Thrown at src/system/history/sync/onboard.rs:288

    request.dry_run = true;
    // Pending decisions belong only to this preview store.
    run::sync(&planning_store, &tracked, &request)?;
    let mut preview = ApplyRequest::automatic();
    preview.automatic = false;
    preview.dry_run = true;
    preview.plan_only = true;
    apply::apply(&planning_store, &tracked, &preview).await?;
    if onboarding.dry_run {
        let preview_config = Some(preview_configuration(&planning_store)?);
        miseprintln!("Dry run: nothing was changed.");
        return Ok(Outcome {
            preview_config,
            durable_access: true,
            setup_held: false,
        });
    }
    if !super::origin::confirmed(onboarding.yes, "Set this machine up from the repository?")? {
        bail!("not set up");
    }

    // Recompute after confirmation against current local files and remote
    // refs; never apply a stale preview or restore over a watcher's new state.
    refuse_other_connection(store, &onboarding.origin, &onboarding.branch)?;
    seed_confirmed_fetch(store, &planning_store)?;
    request.capture = true;
    request.dry_run = false;
    run::sync(store, &tracked, &request)?;

    // the connection: declared machine-locally, recorded for the watcher
    run::update_status(state_dir, run::STATUS_LOCK_WAIT, |status| {
        status.origin_url = Some(onboarding.origin.clone());
        status.origin_branch = Some(onboarding.branch.clone());
        status.disconnected = false;
    })?;
    super::origin::write_config(&onboarding.origin, &onboarding.branch, None)?;
    crate::system::history::notify::warn_if_release_signing_unavailable();

View on GitHub (pinned to afd2eddd3a)

Solutions

1. Complete the initial bootstrap/dotfiles setup before invoking the onboarding step
2. Check that the history store and tracked set are initialized in the state dir
3. Re-run onboarding after setup succeeds

When it happens

Trigger: Thrown at src/system/history/sync/onboard.rs:288 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/87c0e741db14219a. Report an issue: GitHub.