Skip to content

main-broken: developing-today/code id @bd88019 — nix flake check #2186

Closed

Description

@github-actions

Main-tier workflow id failed on main.

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 main in 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.

Activity

  1. github-actions commented on Oct 29, 2026

    @github-actions
    ContributorAuthor

    agent-note:v1 — holder: chain (filing), at 2026-10-29T08:07:00Z. Breakage-ID: 071e97c1ab8c

  2. added
    kind/ciCI/CD pipelines, workflows, and build automation
    priority/criticalDrop everything: main broken, security exposure, repo-wide outage
    queue/queuedHas a queued task in the Supabase agent queue
    on Oct 29, 2026
  3. developing-today commented on Oct 29, 2026

    @developing-today
    Contributor
  4. added
    main-brokenmain branch full-suite (main tier) is red; remediation chain owns this
    on Oct 29, 2026
  5. github-actions commented on Oct 29, 2026

    @github-actions
    ContributorAuthor

    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.

  6. added
    effort/mMedium: expected under 1 day of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    area/ciCI/CD pipelines, workflows, and build automation (area)
    on Oct 29, 2026
  7. dezren39 commented on Oct 29, 2026

    @dezren39
    Member

    Intake review

  8. dezren39 commented on Oct 29, 2026

    @dezren39
    Member

    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.

  9. github-actions commented on Oct 29, 2026

    @github-actions
    ContributorAuthor

    Main is still red for this breakage: https://github.com/developing-today/code/actions/runs/40824449796 (workflow id, head 5a843a1). Breakage-ID: 071e97c1ab8c — appending per the chain dedup rule; no duplicate issue, no duplicate Jules spend.

  10. 105 remaining items

  11. removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    on Nov 4, 2026
  12. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · picked up

    • Agent: queue worker (repo-worker-code), lane code-g
    • Session / ID: task 6603
    • Found via: queue claim (execution lane: direct)
    • Task: task 6603 — CI investigation for issue main-broken: developing-today/code id @bd88019 — nix flake check #2186. Resuming from the standing gate: a completed non-cancelled main id workflow run that makes the treefmt verdict observable.
    • Fresh evidence so far (2026-11-04T13:06Z): the 20 newest main id runs 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 own id run has not appeared yet.
    • Expectation: read run 41816503542's failing jobs, disposition the treefmt verdict, then route task 6603 (fix follow-up or re-park with the verdict recorded).
    • Links: task 6603, issue main-broken: developing-today/code id @bd88019 — nix flake check #2186
  13. added a commit that references this issue on Nov 4, 2026
  14. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · parked

    Fresh verdict (2026-11-04T13:06Z): main id run 41816503542 @60b6dc0a completed with failure — the first readable verdict after days of queued/cancelled runs. Job results: treefmt-check FAIL, clippy-lint FAIL, biome-check FAIL, full (main tier): nix flake check FAIL; 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 of treefmt --config-file ./treefmt.toml --ci reported 0 changed. Fix landed as PR #5456 (format-only, 60 files under pkgs/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-lint fails on deny-level unwrap()/expect() lints — 20 errors in the id lib, 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-check failures 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 main id runs 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.

  15. added
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/claimedQueue worker lifecycle state
    on Nov 4, 2026
  16. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · parked

    Fresh evidence (2026-11-04T13:48Z):

  17. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · parked

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

area/ciCI/CD pipelines, workflows, and build automation (area)effort/mMedium: expected under 1 day of workkind/ciCI/CD pipelines, workflows, and build automationmain-brokenmain branch full-suite (main tier) is red; remediation chain owns thismeta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/criticalDrop everything: main broken, security exposure, repo-wide outagequeue/parkedQueue task is parked (waiting on CI, time, or an event)source/creatorFiled by the new-issue-creator jobstatus/parkedDeliberately paused with a recorded resume conditionstatus:donetask/triageQueue packet kind: verify, reproduce, and route this itemwork/assignedQueue worker lifecycle state

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions