Feature hard docker resource constraints prominently (warning emoji, at minimum) #1307

New issue

Open

opened 2026-07-15 04:14:46 +00:00 by coilysiren · 2 comments

coilysiren commented

2026-07-15 04:14:46 +00:00

Owner

The problem case being that the actual error in here wasn't clear enough

ward-container: wrote codex credentials to /home/ubuntu/.codex/auth.json (scrubbed WARD_CODEX_AUTH_B64 from env)
ward-container: wrote codex config (approvals off, sandbox open, model gpt-5.5 / effort high / verbosity low, 10 trusted dirs) to /home/ubuntu/.codex/config.toml
ward-container: bootstrap agent container composition done
ward-container: fatal: prepare scratch/cache root /gitcache/surface-scratch: only 107.5MiB free of 58.4GiB; need at least 512.0MiB for focused Go verification; recommended cache/temp location is /gitcache/surface-scratch (Go cache root /gitcache/surface-scratch/go-build)
ward: prepare scratch/cache root /gitcache/surface-scratch: only 107.5MiB free of 58.4GiB; need at least 512.0MiB for focused Go verification; recommended cache/temp location is /gitcache/surface-scratch (Go cache root /gitcache/surface-scratch/go-build)
exit status 1

The problem case being that the actual error in here wasn't clear enough --- ``` ward-container: wrote codex credentials to /home/ubuntu/.codex/auth.json (scrubbed WARD_CODEX_AUTH_B64 from env) ward-container: wrote codex config (approvals off, sandbox open, model gpt-5.5 / effort high / verbosity low, 10 trusted dirs) to /home/ubuntu/.codex/config.toml ward-container: bootstrap agent container composition done ward-container: fatal: prepare scratch/cache root /gitcache/surface-scratch: only 107.5MiB free of 58.4GiB; need at least 512.0MiB for focused Go verification; recommended cache/temp location is /gitcache/surface-scratch (Go cache root /gitcache/surface-scratch/go-build) ward: prepare scratch/cache root /gitcache/surface-scratch: only 107.5MiB free of 58.4GiB; need at least 512.0MiB for focused Go verification; recommended cache/temp location is /gitcache/surface-scratch (Go cache root /gitcache/surface-scratch/go-build) exit status 1 ```

coilyco-ops added the

headless

labels

2026-07-15 04:51:13 +00:00

coilyco-ops added this to the warded control plane coherence milestone

2026-07-15 05:14:48 +00:00

coilyco-ops commented

2026-07-15 06:54:30 +00:00

Member

Release triage note from Kai on 2026-07-15: headless carry is valid. This is intentionally text and surfacing work with high impact: hard Docker resource constraints should be prominent enough that agents and operators notice the real failure cause.

coilyco-ops commented

2026-07-15 07:16:39 +00:00

Member

WARD-TRIAGE: warded control plane coherence milestone

This issue is part of the warded control plane coherence sprint. The release thesis is to make warded feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run.

For this sprint, headless means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.

WARD-TRIAGE: warded control plane coherence milestone This issue is part of the `warded control plane coherence` sprint. The release thesis is to make `warded` feel like one dependable control plane for agent work: higher safe parallelism, coherent config defaults, reliable broker/container behavior, human-feedback gates, and enough structured evidence for the next actor after a paused or failed run. For this sprint, `headless` means an engineer should be able to carry the issue from current issue context to a merged change without new human decisions. If the issue discovers a missing decision, split or demote the unclear part instead of guessing.