Repository navigation
Closed
Labels
area/ciCI/CD pipelines, workflows, and build automation (area)CI/CD pipelines, workflows, and build automation (area)effort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/ciCI/CD pipelines, workflows, and build automationCI/CD pipelines, workflows, and build automationmain-brokenmain branch full-suite (main tier) is red; remediation chain owns thismain branch full-suite (main tier) is red; remediation chain owns thismeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/criticalDrop everything: main broken, security exposure, repo-wide outageDrop everything: main broken, security exposure, repo-wide outagequeue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator jobstatus/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume conditionstatus:donetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Description
Main-tier workflow id failed on main.
- Run: https://github.com/developing-today/code/actions/runs/40808190406
- Head commit:
bd88019448ad397cdbcadaf8e0d29171fb1d661d - Failing jobs: nix flake check,nix flake check (cargo-fmt-check),nix flake check (clippy-lint),nix flake check (rustfmt-check),nix flake check (treefmt-check)
- Breakage-ID: 071e97c1ab8c
Filed by the main-breakage chain (.github/workflows/main-broken.yml, #1782). Exactly one holder owns this breakage at a time; every transition is an agent-note:v1 comment on this issue.
Acceptance criteria
- The failing check(s) named in this issue pass on
mainin a linked workflow run, or a fix PR addressing the verified root cause is merged and the follow-up main run is green. - The root cause / breaking change is identified in a comment on this issue (or the failure is documented as infra/flake with evidence and routed as such).
- This issue is closed only with that evidence attached, per the main-breakage chain's holder rules.
Metadata
Metadata
Assignees
Labels
area/ciCI/CD pipelines, workflows, and build automation (area)CI/CD pipelines, workflows, and build automation (area)effort/mMedium: expected under 1 day of workMedium: expected under 1 day of workkind/ciCI/CD pipelines, workflows, and build automationCI/CD pipelines, workflows, and build automationmain-brokenmain branch full-suite (main tier) is red; remediation chain owns thismain branch full-suite (main tier) is red; remediation chain owns thismeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedIntake review done: acceptance criteria, links, and normalized labels addedpriority/criticalDrop everything: main broken, security exposure, repo-wide outageDrop everything: main broken, security exposure, repo-wide outagequeue/parkedQueue task is parked (waiting on CI, time, or an event)Queue task is parked (waiting on CI, time, or an event)source/creatorFiled by the new-issue-creator jobFiled by the new-issue-creator jobstatus/parkedDeliberately paused with a recorded resume conditionDeliberately paused with a recorded resume conditionstatus:donetask/triageQueue packet kind: verify, reproduce, and route this itemQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle stateQueue worker lifecycle state
Activity
github-actions commentedon Oct 29, 2026
agent-note:v1 — holder: chain (filing), at 2026-10-29T08:07:00Z. Breakage-ID: 071e97c1ab8c
developing-today commentedon Oct 29, 2026
CODE-1075
github-actions commentedon Oct 29, 2026
agent-note:v1 — holder: chain (jules budget exhausted) at 2026-10-29T08:07:00Z: 3 open main-broken issues already carry the jules label. This issue carries queue/queued, so the fleet monitor enqueues the priority packet from the issue.
dezren39 commentedon Oct 29, 2026
Intake review
effort/m,meta/enriched).idworkflow runs on main at check time were still in progress, and no merged PR references this breakage. Treated as live; a triage task (queue task 3253, enqueued by this monitor run under Duty 1) owns the verdict.dezren39 commentedon Oct 29, 2026
Correction (fleet monitor): the triage task enqueued for this issue is queue task 3252, not 3253 as stated in the intake review above (3253 is the task for #2165). The monitor's enqueue output arrived after the intake comment was posted; the task itself is correctly deduped to this issue.
github-actions commentedon Oct 29, 2026
Main is still red for this breakage: https://github.com/developing-today/code/actions/runs/40824449796 (workflow
id, head5a843a1). Breakage-ID: 071e97c1ab8c — appending per the chain dedup rule; no duplicate issue, no duplicate Jules spend.105 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
idworkflow run that makes the treefmt verdict observable.idruns are 8 queued, 1 in progress, 6 completed-cancelled, and 5 completed-failure — run 41816503542 @60b6dc0a (10:47Z) has now completed with failure (it was the in-progress run in the previous check), so a verdict run exists to read. Main HEAD is f6de75f (12:54Z); its ownidrun has not appeared yet.Merge pull request #5456 from developing-today/queue/6603-2186-treefm…
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
idrun at or after merge 9fbdbac completes; confirmtreefmt-checkgreen there, then complete task 6603. Clippy/biome/cache items below are separate causes with their own tracks — do not re-fold them into the treefmt fix.Fresh verdict (2026-11-04T13:06Z): main
idrun 41816503542 @60b6dc0a completed with failure — the first readable verdict after days of queued/cancelled runs. Job results:treefmt-checkFAIL,clippy-lintFAIL,biome-checkFAIL,full (main tier): nix flake checkFAIL; PASS: test-shard-1, cargo-check, roc-test, justfmt-check, test-web-typecheck, guard PR check list, arm64 snapshot determinism.Treefmt — root cause and fix (done): the job log shows treefmt traversing 552 files, processing 398, with 59 files changed under
--fail-on-change. Cause is unformatted landings, not formatter/version drift: the flake-pinned treefmt at HEAD 2e55880 reformatted 60 files in fix mode on the laptop, and a verification re-run oftreefmt --config-file ./treefmt.toml --cireported 0 changed. Fix landed as PR #5456 (format-only, 60 files underpkgs/id), merged as 9fbdbac. The drift file-count keeps shifting with landings (67 at filing → 59–60 now) because nothing runs treefmt-check before merge.Clippy — separate cause (not fixed here):
clippy-lintfails on deny-levelunwrap()/expect()lints — 20 errors in theidlib, 521 in lib-test at @60b6dc0a. That is a code-lint backlog, unrelated to formatting; per task 6603 scope it routes separately (see also #803's deferred clippy sweep).Biome — separate cause:
biome-checkfailures are tracked by the per-SHA main-broken biome family (e.g. #5418, #5301, #5229 and siblings), not by this issue.Cache / queue jam — status: Magic Nix Cache throttling (HTTP 418,
ResourceExhausted: rate limit exceeded) is still present in run 41816503542's job logs (cache uploads/downloads) — that cause lives in #774, still OPEN. The run jam is draining, not cleared: of the 20 newest mainidruns at 13:06Z, 5 completed-failure, 6 completed-cancelled, 1 in progress, 8 queued; verdict runs now complete, which is what unblocked this fix.Siblings: #2165, #2163, #2160 re-verified CLOSED this shift — dispositioned as resolved elsewhere; #2186 remains the live tracker for the treefmt family only.
dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
idrun at or after merge 9fbdbac completes; confirmtreefmt-checkgreen there, then complete task 6603.Fresh evidence (2026-11-04T13:48Z):
status:donelabel. The issue closing does not substitute for the post-merge verdict this task is parked on.idrun 41836413833 @9fbdbac0 (created 13:15:15Z) — is still queued, unchanged since creation. No mainidrun at or after 9fbdbac has completed.idruns at 13:48Z: 9 queued, 1 in progress (41821432767 @fef03dd1, pre-merge), 6 completed-cancelled, 4 completed-failure (newest completed is still the pre-merge verdict run 41816503542 @60b6dc0a). Main HEAD is now 49d11b5 (13:46Z), so further verdict runs will queue behind the same jam.dezren39 commentedon Nov 4, 2026
🤖 Agent note · parked
idrun 41836413833 @9fbdbac0 is stillqueued(10 newest mainidruns all queued, zero completed verdict runs at/after the merge). Main has since advanced to 31a00fb. Parking task 6603 again until a mainidrun at/after 9fbdbac completes; then confirm treefmt-check green and complete task 6603.idrun 41836413833 (queued)