Skip to content

main CI failure: Daily Upstream Sync (OpenCode) (run 41903121391) #1672

Open

Description

@dezren39

main CI failure — Daily Upstream Sync (OpenCode)

Failed job 'daily-upstream-sync': step 'Run upstream sync agent via pm-dispatch' failed — pm-dispatch-start: pm-dispatch POST /v1/sessions failed (HTTP 502) (error code: 502), process completed with exit code 1. The follow-on step 'Queue the sync failure via pm-dispatch' also failed — pm-dispatch-queue: pm-dispatch POST /v1/tasks failed (HTTP 502) — so the workflow could not file its own failure tracker for this run (run-id search empty). An earlier run the same hour, 41902737337 (created 2026-11-04T20:02:27Z), failed the same way.

Fresh round: the prior track for this workflow, #1519, was verified CLOSED at 2026-11-04T20:02:04Z, and this run was created 2026-11-04T20:04:50Z (after the closure) — a new failure round with a different failure mode (pm-dispatch HTTP 502, not the prior track's Set-up-job staging-archive failure). No open issue tracked this run (run-id search empty; 'Daily Upstream Sync main' search returned only unrelated #1146).

Filed by main-ci-failure-fix-trigger (fleet). One fix track per failing workflow; duplicates are suppressed until this issue closes.

Log excerpt (gh run view 41903121391 --repo developing-today-forks/opencode --log-failed, error lines)

daily-upstream-sync	Run upstream sync agent via pm-dispatch	2026-11-04T20:05:17.3904756Z ##[error]pm-dispatch-start: pm-dispatch POST /v1/sessions failed (HTTP 502):
daily-upstream-sync	Run upstream sync agent via pm-dispatch	2026-11-04T20:05:17.3905353Z error code: 502
daily-upstream-sync	Run upstream sync agent via pm-dispatch	2026-11-04T20:05:17.3909503Z ##[error]Process completed with exit code 1.
daily-upstream-sync	Queue the sync failure via pm-dispatch	2026-11-04T20:05:20.9346010Z ##[error]pm-dispatch-queue: pm-dispatch POST /v1/tasks failed (HTTP 502):
daily-upstream-sync	Queue the sync failure via pm-dispatch	2026-11-04T20:05:20.9346830Z error code: 502
daily-upstream-sync	Queue the sync failure via pm-dispatch	2026-11-04T20:05:20.9348598Z ##[error]Process completed with exit code 1.

Acceptance criteria

  • The Daily Upstream Sync workflow's dispatch step (pm-dispatch POST /v1/sessions) succeeds again from GitHub Actions, or the failure is shown to be fully explained by the pm-dispatch service outage tracked in pm-dispatch: POST /v1/sessions and /v1/tasks return HTTP 502 (2026-11-04) developing-today/code#5647 and this track closes when that service recovers.
  • A rerun of the workflow on main completes the daily-upstream-sync job (or fails only for an unrelated, separately tracked reason).
  • The failure-handoff step (POST /v1/tasks) also succeeds, so future failures can queue their own tracker.

Activity

  1. added
    kind/bugSomething isn't working (prefixed form of the classic bug label)
    task/small-fixQueue packet kind: bounded fix with reproduction and targeted tests
    priority/highImportant and time-sensitive
    queue/queuedHas a queued task in the Supabase agent queue
    source/ci-watchFiled by the main-CI watch (fleet)
    on Nov 4, 2026
  2. dezren39 commented on Nov 4, 2026

    @dezren39
    Author

    🤖 Agent note · filed

  3. added
    effort/mMedium: expected under 1 day of work
    meta/enrichedIntake review done: acceptance criteria, links, and normalized labels added
    on Nov 4, 2026
  4. dezren39 commented on Nov 4, 2026

    @dezren39
    Author

    Intake review

  5. added
    work/assignedAn agent holds this item via the queue (claimed task)
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    status/parkedDeliberately paused with a recorded resume condition
    and removed
    queue/queuedHas a queued task in the Supabase agent queue
    on Nov 5, 2026
  6. 6 remaining items

  7. added
    queue/claimedA queue worker has claimed the task for this item
    queue/blockedQueue task is blocked (reason recorded on the task)
    status/blockedBlocked on something named in the issue/PR
    user/escalatedMuse reviewed it; the decision is genuinely the user's — escalated with Muse's read attached
    and removed
    status/parkedDeliberately paused with a recorded resume condition
    queue/parkedQueue task is parked (waiting on CI, time, or an event)
    queue/claimedA queue worker has claimed the task for this item
    work/assignedAn agent holds this item via the queue (claimed task)
    on Nov 5, 2026
  8. dezren39 commented on Nov 5, 2026

    @dezren39
    Author

    🤖 Agent note · picked-up

  9. dezren39 commented on Nov 5, 2026

    @dezren39
    Author

    🤖 Agent note · blocked

  10. dezren39 commented on Nov 5, 2026

    @dezren39
    Author

    🤖 Agent note · escalated

    • Agent: repo-worker-opencode
    • Session / ID: ses_e5e52fd3fcdffeDjsOdrj5VYQw / task 9734 / lane 3fe37e8a-c61b-419c-9e97-769ecd264d5d
    • Escalation: Service code is fixed, but the deployment needs an interactive privileged operation this worker cannot perform. The queue task is blocked as escalated-to-user.
    • Decision/action needed: Drew or a root operator runs sudo nixos-rebuild switch --flake /home/user/code#amd, verifies pm-tunnel is on HTTP/2 and dispatch endpoints recover, then permits a fresh workflow run.
  11. removed
    status/blockedBlocked on something named in the issue/PR
    queue/blockedQueue task is blocked (reason recorded on the task)
    on Nov 5, 2026
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

    effort/mMedium: expected under 1 day of workkind/bugSomething isn't working (prefixed form of the classic bug label)meta/enrichedIntake review done: acceptance criteria, links, and normalized labels addedpriority/highImportant and time-sensitivesource/ci-watchFiled by the main-CI watch (fleet)task/small-fixQueue packet kind: bounded fix with reproduction and targeted testsuser/escalatedMuse reviewed it; the decision is genuinely the user's — escalated with Muse's read attached

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions