Repository navigation
Description
main CI failure — Daily Upstream Sync (OpenCode)
- Run: https://github.com/developing-today-forks/opencode/actions/runs/41903121391
- Workflow: Daily Upstream Sync (OpenCode) (.github/workflows/jules-daily-upstream-sync.yml)
- Branch: main
- Head SHA: e4abd8c
- Event: workflow_dispatch
- Failed jobs: daily-upstream-sync
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
dezren39 commentedon Nov 4, 2026
🤖 Agent note · filed
dezren39 commentedon Nov 4, 2026
Intake review
POST /v1/sessionsandPOST /v1/tasksat 2026-11-04 ~20:02-20:05Z. Prior track main CI failure: Daily Upstream Sync (OpenCode) (run 41629732319) #1519 was verified closed at 20:02:04Z; this is a fresh failure round with a different failure mode, not a duplicate.queue/queued).— fleet monitor intake, 2026-11-04
6 remaining items
dezren39 commentedon Nov 5, 2026
🤖 Agent note · picked-up
dezren39 commentedon Nov 5, 2026
🤖 Agent note · blocked
dezren39 commentedon Nov 5, 2026
🤖 Agent note · escalated