xai-org/grok-build · error

targeted fetch task failed: {e}

Error message

targeted fetch task failed: {e}

What it means

This error wraps any failure returned by the spawned async targeted-fetch task. The wrapper awaits a `JoinHandle`; if the task itself completes with `Err(e)`, the original error is re-wrapped as `AsyncFetchOutcome::Completed(Err(...))` with the message 'targeted fetch task failed: {e}', so the root cause (network, auth, ref not found, etc.) is in the formatted `{e}`.

Source

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

async fn spawn_targeted_fetch(git_root: &Path, spec: &str, kind: FetchKind) -> AsyncFetchOutcome {
    let fetch_root = git_root.to_path_buf();
    let fetch_spec = spec.to_owned();
    match tokio::time::timeout(
        crate::restore_fetch::RESTORE_FETCH_BUDGET + crate::restore_fetch::RESTORE_FETCH_JOIN_SLACK,
        tokio::task::spawn_blocking(move || match kind {
            FetchKind::CheckoutRef => {
                crate::restore_fetch::fetch_checkout_target_if_missing(&fetch_root, &fetch_spec)
            }
            FetchKind::CommitOidOnly => {
                crate::restore_fetch::fetch_commit_if_missing(&fetch_root, &fetch_spec)
            }
        }),
    )
    .await
    {
        Err(_) => AsyncFetchOutcome::Abandoned,
        Ok(Err(e)) => {
            AsyncFetchOutcome::Completed(Err(anyhow::anyhow!("targeted fetch task failed: {e}")))
        }
        Ok(Ok(result)) => AsyncFetchOutcome::Completed(result),
    }
}
/// Checkout `head_commit` (full oid or simple ref), fetching from origin if needed.
pub(crate) async fn checkout_commit_with_fetch(
    git_root: &Path,
    head_commit: &str,
    stash_if_dirty: bool,
) -> CheckoutCommitResponse {
    if let Some(current) = get_current_commit(git_root).await
        && current == head_commit
        && git_cli(git_root, &["cat-file", "-t", head_commit])
            .await
            .is_ok()
    {
        return CheckoutCommitResponse {
            checked_out: true,

View on GitHub (pinned to bc7f02eddd)

Solutions

1. Read the wrapped `{e}` in the message to find the root cause
2. Run `git fetch origin <ref>` manually in the workspace to reproduce and see git's stderr
3. Fix credentials (refresh token, `ssh-add`) or network/proxy settings
4. Verify the target branch/ref still exists on origin

Example fix

null

let out = std::process::Command::new("git").args(["ls-remote","origin"]).output()?;
if !out.status.success() { eprintln!("remote unreachable: {}", String::from_utf8_lossy(&out.stderr)); }

match outcome {
    AsyncFetchOutcome::Completed(Err(e)) if e.to_string().contains("targeted fetch task failed") => {
        // inspect root cause in {e}: retry with backoff or surface to user
    }
    _ => {}
}

When it happens

Trigger: The inner fetch future fails for any reason — remote unreachable, bad SSH/HTTPS credentials, missing refspec, or non-zero `git fetch` exit — during the targeted fetch used before checkout.

Common situations: Offline or firewalled environment; expired GitHub token / SSH key not loaded; fetching a branch deleted on the remote; proxy misconfiguration.

Related errors

• git fetch --no-tags origin {spec} failed ({status}): {stderr
• fetch of base ref '{base}' failed: {fetch_out}
• Failed to push tag: {stderr}
• git fetch origin {oid} skipped: restore fetch budget exhaust
• unsupported checkout target (need a full commit oid or a sim

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