xai-org/grok-build · error

fetch of base ref '{base}' failed: {fetch_out}

Error message

fetch of base ref '{base}' failed: {fetch_out}

What it means

Sync-base fetches `origin <base>` and requires the fetch to succeed before computing merge relationships. `git_cli_raw_mut` returns (success, output); if git exits non-zero, the command output is surfaced as this error so the caller sees why `git fetch origin <base>` failed.

Source

Thrown at crates/codegen/xai-grok-workspace/src/session/git.rs:3047

            "merge --abort failed: {out}"
        );
        return Ok(GitSyncBaseResult {
            outcome: GitSyncBaseOutcome::Aborted,
        });
    }
    ensure_on_branch(git_root, expected_branch).await?;
    anyhow::ensure!(
        !merge_in_progress(git_root).await?,
        "a merge is already in progress; resolve it or call again with abort"
    );
    let dirty = git_cli(git_root, &["status", "--porcelain"]).await?;
    anyhow::ensure!(
        dirty.is_empty(),
        "working tree is not clean; commit or discard changes before syncing the base"
    );
    let base = base_ref.unwrap_or("HEAD");
    let (fetched, fetch_out) = git_cli_raw_mut(git_root, &["fetch", "origin", base]).await?;
    anyhow::ensure!(fetched, "fetch of base ref '{base}' failed: {fetch_out}");
    if git_cli_raw(
        git_root,
        &["merge-base", "--is-ancestor", "FETCH_HEAD", "HEAD"],
    )
    .await?
    .0
    {
        return Ok(GitSyncBaseResult {
            outcome: GitSyncBaseOutcome::UpToDate,
        });
    }
    let (merged, merge_out) =
        git_cli_raw_mut(git_root, &["merge", "--no-edit", "FETCH_HEAD"]).await?;
    if merged {
        let sha = git_cli(git_root, &["rev-parse", "HEAD"]).await?;
        return Ok(GitSyncBaseResult {
            outcome: GitSyncBaseOutcome::Merged { sha },
        });

View on GitHub (pinned to bc7f02eddd)

Solutions

1. Check the fetch stderr in `{fetch_out}` for the concrete cause
2. Verify the remote exists: `git remote -v`; add it with `git remote add origin <url>` if missing
3. Refresh credentials (token, `ssh-add`) and test connectivity (`git ls-remote origin`)
4. Confirm the base ref exists on origin (`git ls-remote origin <base>`) and retry

Example fix

// before
// no origin remote configured
sync_base(&git_root, req)
// after
// terminal: git remote add origin git@github.com:org/repo.git
sync_base(&git_root, req)

let ls = Command::new("git").args(["ls-remote","origin"]).current_dir(git_root).output()?;
if !ls.status.success() { return Err(format!("origin unreachable: {}", String::from_utf8_lossy(&ls.stderr))); }

match sync_base(...).await {
    Err(e) if e.to_string().contains("fetch of base ref") => {
        // transient? retry with backoff; otherwise fix remote/credentials per message
    }
    r => r?,
}

When it happens

Trigger: The `origin` remote is missing, unreachable, or unauthenticated; the base ref does not exist on origin; network/proxy failure; shallow or restricted clone lacking the ref.

Common situations: Repo cloned without an `origin` remote (local-only); expired credentials or missing SSH key; base branch deleted upstream; corporate proxy blocking git traffic.

Related errors

• git fetch --no-tags origin {spec} failed ({status}): {stderr
• targeted fetch task failed: {e}
• merge into '{target_branch}' succeeded but push failed ({sta
• Failed to push tag: {stderr}
• git fetch origin {oid} skipped: restore fetch budget exhaust

AI-assisted analysis of xai-org/grok-build@bc7f02eddd (2026-08-31). Data as JSON: /api/errors/9e1f65a2ff26684c. Report an issue: GitHub.