Zackriya-Solutions/meetily · error · anyhow::Error

{} response exceeds its exact {} byte size

Error message

{} response exceeds its exact {} byte size

What it means

The server's response body for a model artifact exceeded the exact byte size declared in the download catalog. The downloader enforces strict size accounting and aborts rather than writing more bytes than expected, treating the mismatch as an integrity problem (wrong or tampered file).

Source

Thrown at frontend/src-tauri/src/parakeet_engine/parakeet_engine.rs:1040

                                "Failed to preserve {} after stream error: {}",
                                artifact.filename,
                                flush_error
                            )
                        })?;
                        return Err(anyhow!("Download stream failed for {}: {}", artifact.filename, error));
                    }
                    Ok(Some(Ok(chunk))) => chunk,
                };

                let chunk_bytes = chunk.len() as u64;
                let next_artifact_bytes = artifact_bytes
                    .checked_add(chunk_bytes)
                    .ok_or_else(|| anyhow!("{} size overflow", artifact.filename))?;
                if next_artifact_bytes > artifact.exact_bytes {
                    writer.flush().await.map_err(|error| {
                        anyhow!("Failed to preserve {} after overlong response: {}", artifact.filename, error)
                    })?;
                    return Err(anyhow!(
                        "{} response exceeds its exact {} byte size",
                        artifact.filename,
                        artifact.exact_bytes
                    ));
                }
                let next_confirmed_bytes = confirmed_bytes
                    .checked_add(chunk_bytes)
                    .ok_or_else(|| anyhow!("Progress overflow while downloading {}", artifact.filename))?;
                if next_confirmed_bytes > total_bytes {
                    return Err(anyhow!("Download progress exceeds the catalog total"));
                }

                writer
                    .write_all(&chunk)
                    .await
                    .map_err(|error| anyhow!("Failed to write {}: {}", artifact.filename, error))?;
                artifact_bytes = next_artifact_bytes;
                confirmed_bytes = next_confirmed_bytes;

View on GitHub (pinned to a2cb62e827)

Solutions

  1. Update the catalog manifest so exact_bytes matches the file actually served by the server
  2. Purge/refresh the CDN or proxy cache for the model URL and retry
  3. Verify with curl -I (Content-Length) that the server response matches the declared exact_bytes
  4. Clear the partial local file and retry in case of a corrupted mixed stream

Example fix

// before
"exact_bytes": 151847968
// after
// recompute after re-uploading the model
"exact_bytes": <actual file size from sha256sum/ls -l of served artifact>
Defensive patterns

Strategy: validation

Validate before calling

// verify the server-declared size matches the catalog before streaming
let head = client.head(&file_url).send().await?;
let content_length: u64 = head.headers()[reqwest::header::CONTENT_LENGTH]
    .to_str()?.parse()?;
anyhow::ensure!(content_length == artifact.exact_bytes,
    "server serves {} bytes but catalog declares {}", content_length, artifact.exact_bytes);

Try / catch

match result {
    Err(e) if e.to_string().contains("exceeds its exact") => {
        // size mismatch: refresh catalog, purge CDN cache, then revalidate
        refresh_catalog_and_retry()
    }
    other => other,
}

Prevention

When it happens

Trigger: A chunk arrives when artifact_bytes already equals exact_bytes and next_artifact_bytes > artifact.exact_bytes at parakeet_engine.rs:1036-1044: server sent a Content-Length/body larger than catalog, a proxy injected extra data, or the artifact entry in the catalog has a stale/incorrect exact_bytes value.

Common situations: Model was re-uploaded to the server but the catalog's exact_bytes wasn't updated; CDN serving a stale or wrong object; misconfigured reverse proxy appending data; user edited the model manifest.

Related errors

AI-assisted analysis of Zackriya-Solutions/meetily@a2cb62e827 (2026-09-12). Data as JSON: /api/errors/fbcfcc2e9021e164. Report an issue: GitHub.