zed-industries/zed · error · anyhow::Error

Failed to reset:\n{}

Error message

Failed to reset:\n{}

What it means

The 'git reset --mixed/--soft <commit>' subprocess completed but exited non-zero; the error embeds git's output ({}). Reset failed due to repository state — unmerged index, index.lock held by another process, or an invalid commit ref — while spawning itself succeeded.

Source

Thrown at crates/git/src/repository.rs:1513

                .stdin(Stdio::piped())
                .stdout(Stdio::piped())
                .stderr(Stdio::piped())
                .spawn()
                .context("starting git cat-file process")?;

            let mut files = Vec::<CommitFile>::new();
            let stdin = cat_file_process
                .stdin
                .take()
                .context("git cat-file process has no stdin")?;
            let stdout = cat_file_process
                .stdout
                .take()
                .context("git cat-file process has no stdout")?;
            let mut stdin = BufWriter::with_capacity(512, stdin);
            let mut stdout = BufReader::new(stdout);
            let mut info_line = String::new();
            let mut newline = [b'\0'];
            for change in changes {
                let change = change?;
                let path = change.path;
                // git-show outputs `/`-delimited paths even on Windows.
                let Some(rel_path) = RelPath::from_unix_str(path).log_err() else {
                    continue;
                };

                let objects = [change.new_object, change.old_object];
                let mut has_blobs = false;
                for object in objects.iter().flatten() {
                    if object.kind == CommitDiffObjectKind::Blob {
                        stdin.write_all(object.oid.as_bytes()).await?;
                        stdin.write_all(b"\n").await?;
                        has_blobs = true;
                    }
                }
                if has_blobs {

View on GitHub (pinned to 5a9b9558db)

Solutions

1. Read the embedded git output: 'Unable to create index.lock' means another git process is running — retry after it finishes
2. For unmerged paths, resolve conflicts before resetting
3. Validate the commit ref exists in this repository before issuing the reset

When it happens

Trigger: Thrown at crates/git/src/repository.rs:1502 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zed-industries/zed@5a9b9558db (2026-08-20). Data as JSON: /api/errors/97a55b2e78510f7a. Report an issue: GitHub.