jdx/mise · error

not connected

Error message

not connected

What it means

State precondition in origin operations (set_inner): the machine has no configured history origin — no repository connection exists — so a disconnect/sync action targeting the origin has nothing to act on. This is a sentinel bail for 'no origin configured'.

Source

Thrown at src/system/history/sync/origin.rs:178

            differing.len()
        );
        for path in differing.iter().take(10) {
            miseprintln!("  differs: {path}");
        }
    }
    miseprintln!(
        "All committed versions of explicitly tracked files are eligible for synchronization. Untracking does not erase earlier versions."
    );
    let config_dir = crate::system::history::tracked::global_config_dir();
    if config_dir.join(".git").exists() {
        miseprintln!(
            "{} is a git checkout: enabling history does not convert or migrate it; applied files appear there as ordinary working-tree changes.",
            display_path(&config_dir)
        );
    }
    let mut status = run::read_status(state_dir)?;
    if !confirmed(opts.yes, "Connect this setup repository?")? {
        bail!("not connected");
    }
    *accepted = true;

    // the mode is recorded only when it differs from what the settings
    // say, so `mise settings set history.sync …` keeps working afterwards
    let mode =
        (opts.mode.as_str() != crate::config::Settings::get().history.sync).then_some(opts.mode);
    write_config(&opts.url, &opts.branch, mode)?;
    // another repository or branch starts from a clean slate: the previous
    // one's per-path state, pending changes, and conflicts would read its
    // absence of a file as a deletion
    if connected_before && !same_origin {
        reset_sync_state(repo)?;
        status = run::SyncStatus::default();
        info!(
            "history: a different setup repository; the previous one's sync state is discarded (local checkpoints are kept)"
        );
    }

View on GitHub (pinned to afd2eddd3a)

Solutions

1. Run `mise bootstrap dotfiles origin set <url>` to connect a repository first
2. Verify the global config file contains a [history.origin] table
3. Re-run the origin operation after connecting

When it happens

Trigger: Thrown at src/system/history/sync/origin.rs:178 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/323a2797967a5e54. Report an issue: GitHub.