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

Closed

opened 2026-07-15 04:14:46 +00:00 by coilysiren · 3 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

autonomy

headless

priority

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

Owner

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

Owner

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.

coilyco-ops commented

2026-07-15 12:53:51 +00:00

Owner

WARDED_WORKFLOW: reservation-held

reservation details

Holder: launch intent for container engineer-codex-ward-1307 on host kais-macbook-pro-2.local.

Accepted by ward agent --harness codex (reserved 2026-07-15T12:53:50Z). Concurrent ward agent runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). --override-reservation overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)

Resolved: coilyco-flight-deck/ward#1307 · branch issue-1307 · harness codex · workflow pull-request-and-merge
Run: engineer-codex-ward-1307 · ward v0.710.0 · dispatched 2026-07-15T12:53:39Z
Comment thread: 2 included in the pre-flight read, 0 stripped (ward's own automated comments).
- included: @coilyco-ops (2026-07-15T06:54:30Z), @coilyco-ops (2026-07-15T07:16:39Z)

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0).

— Codex, via ward agent

WARDED_WORKFLOW: reservation-held <details><summary>reservation details</summary> Holder: launch intent for container `engineer-codex-ward-1307` on host `kais-macbook-pro-2.local`. Accepted by `ward agent --harness codex` (reserved 2026-07-15T12:53:50Z). Concurrent `ward agent` runs are blocked until this intent becomes visible or the intent is released. The stale-intent fallback is still TTL-bounded (3h TTL). `--override-reservation` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/ward#1307` · branch `issue-1307` · harness `codex` · workflow `pull-request-and-merge` - **Run:** `engineer-codex-ward-1307` · ward `v0.710.0` · dispatched `2026-07-15T12:53:39Z` - **Comment thread:** 2 included in the pre-flight read, 0 stripped (ward's own automated comments). - included: @coilyco-ops (2026-07-15T06:54:30Z), @coilyco-ops (2026-07-15T07:16:39Z) Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.710.0). </details> </details>  — Codex, via `ward agent`

coilyco-ops referenced this issue from a pull request that will close it,

2026-07-15 12:56:59 +00:00

Feature hard docker resource constraints prominently #1441

coilyco-ops closed this issue

2026-07-15 12:58:29 +00:00

coilyco-ops referenced this issue

2026-07-15 13:08:07 +00:00

Recover release setup after GitHub action fetch timeout #1443

Commenting is not possible because the repository is archived.