Skip to content

main-broken: developing-today/code nix ci @72efce0 — basic: proxy port fallbacks #5273

Closed

Description

@developing-today

Main-tier workflow nix ci 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.
Diagnose the failure, fix the root cause, and deliver the fix as a pull request whose description contains "Fixes #", using the number of the issue this dispatch created, so the issue closes when the fix lands.

Activity

  1. developing-today commented on Nov 4, 2026

    @developing-today
    ContributorAuthor

    Filed by pm-dispatch (GitHub Actions OIDC (repo developing-today/code, actor dezren39, workflow developing-today/code/.github/workflows/main-broken.yml@refs/heads/main)).

    • Queue task: #9155 (repo-health-code-pilot, kind: triage, priority: 40)
    • Status: queued
  2. added
    kind/ciCI/CD pipelines, workflows, and build automation
    priority/criticalDrop everything: main broken, security exposure, repo-wide outage
    main-brokenmain branch full-suite (main tier) is red; remediation chain owns this
    on Nov 4, 2026
  3. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    agent-note:v1 — holder: chain (filing), at 2026-11-04T03:51:30Z. Breakage-ID: 920071b5cd60

  4. added
    julesHand this issue to Jules (issue-labeled job in jules.yml)
    on Nov 4, 2026
  5. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    agent-note:v1 — holder: jules, since 2026-11-04T03:51:43Z (jules label applied; the issue-labeled job in jules.yml starts remediation via pm-dispatch). Remediation budget at filing: 2/3 concurrent remediations in flight.

  6. developing-today commented on Nov 4, 2026

    @developing-today
    ContributorAuthor

    Filed by pm-dispatch (GitHub Actions OIDC (repo developing-today/code, actor dezren39, workflow developing-today/code/.github/workflows/main-broken.yml@refs/heads/main)).

    • Queue task: #9158 (repo-health-code-pilot, kind: triage, priority: 40)
    • Status: queued
  7. developing-today commented on Nov 4, 2026

    @developing-today
    ContributorAuthor

    Filed by pm-dispatch (GitHub Actions OIDC (repo developing-today/code, actor dezren39, workflow developing-today/code/.github/workflows/main-broken.yml@refs/heads/main)).

    • Queue task: #9160 (repo-health-code-pilot, kind: triage, priority: 40)
    • Status: queued
  8. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    Main is still red for this breakage: https://github.com/developing-today/code/actions/runs/41732734968 (workflow nix ci, head 5c53272). Breakage-ID: 920071b5cd60 — appending per the chain dedup rule; no duplicate issue. A fresh fix task has been queued on this issue via pm-dispatch.

  9. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    Main is still red for this breakage: https://github.com/developing-today/code/actions/runs/41733487577 (workflow nix ci, head 07168f9). Breakage-ID: 920071b5cd60 — appending per the chain dedup rule; no duplicate issue. A fresh fix task has been queued on this issue via pm-dispatch.

  10. developing-today commented on Nov 4, 2026

    @developing-today
    ContributorAuthor

    Filed by pm-dispatch (GitHub Actions OIDC (repo developing-today/code, actor dezren39, workflow developing-today/code/.github/workflows/main-broken.yml@refs/heads/main)).

    • Queue task: #9163 (repo-health-code-pilot, kind: triage, priority: 40)
    • Status: queued
  11. 100 remaining items

  12. github-actions commented on Nov 4, 2026

    @github-actions
    Contributor

    Main is still red for this breakage: https://github.com/developing-today/code/actions/runs/41754060893 (workflow nix ci, head 7dd1b54). Breakage-ID: 920071b5cd60 — appending per the chain dedup rule; no duplicate issue. A fresh fix task has been queued on this issue via pm-dispatch.

  13. added
    work/assignedQueue worker lifecycle state
    queue/claimedQueue worker lifecycle state
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 4, 2026
  14. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · picked up

  15. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · done

    Root cause. .github/scripts/check-proxy-port-fallbacks.sh guards that every proxy port literal in bin/<name>-proxy.mjs and .opencode/opencode.jsonc matches the let-block definition in home/common/default.nix. Commit 7b51087 removed the design-code door (:18746) — its designCodeProxyPort let and unit — and 1dad07b retired the codex provider from opencode.jsonc, but the guard's table still carried both rows. Every nix-ci run in that window failed with (run 41753551897 @d0a5b03, job log):

    • .opencode/opencode.jsonc has no {env:CODEX_PROXY_PORT:-18744} baseURL … (#434)
    • designCodeProxyPort definition not found in home/common/default.nix.

    Fix already landed. f6e303d "ci: retire stale proxy-port guard rows for the removed design-code door and the retired codex provider (#5240)" removed the design-code row and set the CODEX row to has_config "no" (its let + bin/codex-proxy.mjs fallback checks remain).

    Verification (fresh, this run).

    • The guard script run against current main (6ed2ae7) exits 0: "proxy port fallbacks match the home/common/default.nix definitions (7 proxies)."
    • Recent completed nix ci runs on main are green including this job: run 41771870602 @85c0e0b success, run 41770934029 @12fcad9 success, run 41770535981 @eb36246 success.
    • The @72efce0 in this issue's title predates f6e303d (the fix is not an ancestor of 72efce0), so it is the same pre-fix window, not a post-fix recurrence.

    Closing as already-fixed. The sibling dispatch task 9259 (@f486f2a, same breakage window) can complete on this evidence.

  16. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · done

  17. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · done

    Issue #5273 is CLOSED and the breakage is fixed on main: the stale proxy-port guard rows were retired in commit f6e303d (#5240), verified this shift under task 9288 on the sibling holder issue #5265 — the guard script passes against clean origin/main (exit 0, 7 proxies match) and every red run was a pre-fix tree executed late from the CI backlog. Full diagnosis is on issue #5265 (comment 6624479463). Completing task 9261 as already_done; no new work needed.

  18. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · done

  19. dezren39 commented on Nov 4, 2026

    @dezren39
    Member

    🤖 Agent note · done

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    julesHand this issue to Jules (issue-labeled job in jules.yml)kind/ciCI/CD pipelines, workflows, and build automationmain-brokenmain branch full-suite (main tier) is red; remediation chain owns thispriority/criticalDrop everything: main broken, security exposure, repo-wide outagesource/dispatchFiled by pm-dispatch

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions