zeroclaw-labs/zeroclaw · error · anyhow::Error

SHA256SUMS fetch returned {}

Error message

SHA256SUMS fetch returned {}

What it means

Error "SHA256SUMS fetch returned {}" thrown in zeroclaw-labs/zeroclaw.

Source

Thrown at src/commands/update.rs:515

    Ok(())
}

async fn verify_download_checksum(
    bytes: &[u8],
    asset_url: &str,
    sha256sums_url: &str,
    client: &reqwest::Client,
) -> Result<()> {
    let asset_name = asset_name_from_url(asset_url)
        .context("cannot derive release asset filename from download URL")?;

    let sums_resp = client
        .get(sha256sums_url)
        .send()
        .await
        .context("failed to fetch SHA256SUMS")?;
    if !sums_resp.status().is_success() {
        bail!("SHA256SUMS fetch returned {}", sums_resp.status());
    }

    let sums_text = sums_resp
        .text()
        .await
        .context("failed to read SHA256SUMS body")?;
    verify_checksum_bytes(bytes, &asset_name, &sums_text)?;

    ::zeroclaw_log::record!(
        INFO,
        ::zeroclaw_log::Event::new(module_path!(), ::zeroclaw_log::Action::Note)
            .with_outcome(::zeroclaw_log::EventOutcome::Success)
            .with_attrs(::serde_json::json!({"asset": asset_name})),
        "Update download checksum verified"
    );
    Ok(())
}

View on GitHub (pinned to 88bb9c8533)

Solutions

1. Check connectivity to the release host serving SHA256SUMS and retry.
2. If the release lacks a SHA256SUMS file, update to a release that publishes checksums or verify manually.

When it happens

Trigger: Thrown at src/commands/update.rs:515 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of zeroclaw-labs/zeroclaw@88bb9c8533 (2026-08-23). Data as JSON: /api/errors/ca817fdbaed37e2b. Report an issue: GitHub.