{% extends "_layout.html" %} {% set title = "Archive rejected" %} {% set status = "422 Unprocessable Content" %} {% set description = "The archive broke a normative limit or cannot be run as sent. reason names which." %} {% set also_on_a_job = true %} {% block main %}
While the job stages, the uploaded archive broke one of the rules an archive must follow, or cannot be run as sent. The job is rejected, with this on its error.
reason, and fix what it names, in a new job.member_count and expanded_bytes are published limits (max_archive_members, max_archive_expanded_bytes): send less.ratio is an early abort on the compression ratio, where the deployment applies one. link_member, device_member and traversal are safety rules: the archive carries a link that resolves outside it, a device file, or a member named with .., written twice, or written through a link. A link that resolves inside the archive is kept as a link. A client builds none of these; a hand-built archive can.missing_manifest and invalid_manifest: the archive holds no manifest at its root, or one that cannot be read. invalid_manifest also names a member stored sparse, by GNU’s old S type or a GNU.sparse pax record, since extracting one and reading it can disagree about its bytes. A client never writes one; a hand-built archive can. The reference sc-server reads each member as a file and does not refuse one.credential: a dataroot’s path in a manifest the archive carries — the root one, or an upstream node’s under <step>/<index>/outputs/ — carries userinfo: user@ or user:secret@ ahead of its host. keypath names the first such dataroot and detail names each, never by value. A client sends every dataroot’s path without it, so this is a client bug. The server cannot remove the credential from an archive it would keep as uploaded, so it keeps none of it: the upload is deleted, and only the record of why is kept. Register the dataroot without it, and give the credential through the environment on your own machine.unrequested_member is a member the server did not ask for: in the first archive, anything but the manifest, sc_collected_files/ and <step>/<index>/outputs/ for a node the run reads and does not run, a value under a private dataroot included — which carries that dataroot’s keypath, and whose upload is not kept; in a follow-up — one sent after the server asked in upload_sources — a dataroot or a wheel it did not ask for.missing_member is the opposite: the flow reads a value the client should have sent, or the results of a node the run reads and does not run, and nothing supplies it. detail names the keypath or the node. A client sends what the flow’s tasks require, so this is a client bug, or a task whose requirements leave out a file it reads.python_package is an uploaded wheel, under sc_collected_files/python/, that is not pure — tagged none-any, with no .so, .pyd or .dylib — is malformed, overlaps a distribution python_packages lists or another wheel, or arrives on a deployment without python.env. detail names the wheel. The client builds every wheel, so this is a client bug.breakpoint is a node with option,breakpoint set: the run would stop for a person to look, and nobody is at a remote run. detail names the node. Clear the breakpoint for it.interactive_task is a node whose task opens a window for a person — every ShowTask, OpenROAD’s WebTask — which nobody is at a remote run to use. detail names the node and its task. A ScreenshotTask renders the same view headless and is allowed.extension is a member whose file extension the deployment’s allowlist does not admit. detail names the member. That is deployment policy, not a safety rule: only a deployment with a member-extension allowlist raises it. The reference sc-server has none — it admits every extension — and never raises it.{
"id": "01J9...",
"state": "rejected",
"error": {
"type": "https://sc.example.com/server-errors/archive-rejected",
"title": "Archive rejected",
"status": 422,
"detail": "...",
"reason": "expanded_bytes" // REQUIRED on this type
}
}
| Member | ||
|---|---|---|
reason | REQUIRED | member_count, expanded_bytes, ratio, link_member, device_member, traversal, missing_manifest, invalid_manifest, credential, unrequested_member, missing_member, python_package, breakpoint, interactive_task or extension. An unrecognised value means act on the type alone. |
keypath | optional | On credential, and on unrequested_member for a private dataroot’s value: the dataroot, as SiliconCompiler keeps it — a library’s ["library", name, "dataroot", root] or a task’s ["tool", tool, "task", task, "dataroot", root]. Absent on every other reason. |
detail is prose and may be reworded at any time. Branch on type, then on reason — never parse detail.
GET /v1/jobs/{id} |
As a rejected job’s error: found while the job stages, after submit answered 202 — the first archive or a follow-up. |
upload-too-large is the archive being too large to accept at all.
upload-forbidden is a policy about the restricted material an archive carries — whose it is, not what shape the archive takes — and not a safety failure.