Keyboard shortcuts

Press ← or → to navigate between chapters

Press S or / to search in the book

Press ? to show this help

Press Esc to hide this help

Internal (store, protocol, I/O)

Messages below show representative example values (paths, targets, names); the real message carries yours.

ATC-E0001

protocol: frame too large (999 bytes, max 100)
  • exit code: 1

ATC-E0100

store: push failed: Materialize("ATC-E0100: I/O error: Operation not permitted (os error 1)"); artifact=app
  • exit code: 1

ATC-E0102

store: schema migration failed at step 3: bad schema
  • exit code: 1

ATC-E0442

protocol: broken pipe
  • exit code: 1

ATC-E0443

The catch-all for a command failure that has no more specific code. The failure is not always in the local store: the text after store: names the step that failed and its cause, and that text is the lead. A failure to download or verify an atc update has its own code, ATC-E0472 or ATC-E0473. A control plane that atc cannot reach has its own code, ATC-E0474. A failed atc diagnose send has its own code, ATC-E0478.

store: push failed: lifecycle veto at commit.enter
  • exit code: 1

ATC-E0444

io: disk full
  • exit code: 1

ATC-E0453

io: failed to write output: stdout closed
  • exit code: 1

ATC-E0456

internal error: no daemon-ensure behavior was wired in for an SSH-path command (socket is None); this is a caller bug, not a daemon response
  • exit code: 1

ATC-E0457

internal error: resolve_connect_target was called with no SSH target and no --socket; this is a caller bug, not a daemon or config problem
  • exit code: 1