You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Between ~05:25Z and ~05:41Z on 2026-11-09, every CI step that downloads a release asset from https://github.com/<org>/<repo>/releases/download/... failed with 504 Gateway Time-out. The default branches of both repositories were green minutes earlier (hivecommons/docs main at a846221, 03:57Z: FOSSA + TypeScript & Lint Check both success), and the diffs of the affected PRs do not touch the failing steps. This is one GitHub-side incident, not N PR-local failures.
Affected PRs are deferred and stamped <!-- hive-shared-ci-N --> so they can be re-run once GitHub release downloads recover; no PR-local repair is warranted.
Re-running the failed jobs is out of this lane's write tier (gh run rerun not permitted) — a maintainer re-run or a fresh push will clear them.
Close this issue once the affected checks are green again.
Scanner decision: no code change proposed. Adding GHCR/mirror fallbacks for these downloads would be speculative for a transient outage.
Checked at 05:50Z: GitHub release-asset downloads have recovered — crate-ci/typos/releases/download/v1.52.0/...musl.tar.gz, fossas/fossa-cli/releases/latest and golangci/golangci-lint/releases/latest all return HTTP 200 now.
No repository change is needed: this was a GitHub-side 504 incident, and the Dockerfile fetch already retries (15 attempts). The failed jobs only need a re-run, which my token can't trigger (no push/triage on hivecommons/hive or hivecommons/docs):
Update 06:05Z — not fully recovered; v5 default branch is now red from the same cause.
v5 push run 42569566088 (7491bb0, 05:50Z) failed in docker (hive) at src/Dockerfile stage [runtime 8/74] (gh CLI install): curl: (22) The requested URL returned error: 504 on cli/cli/releases/download/v2.103.3/gh_2.103.3_linux_amd64.tar.gz, despite --retry 30 --retry-all-errors over 300 s.
Probed at 06:03–06:05Z: the 504 is per-asset and persistent, not a blanket outage. casey/just/.../1.58.0/just-1.58.0-x86_64-unknown-linux-musl.tar.gz and the gh 2.103.3 amd64 tarball return HTTP/2 504 on every attempt (headers carry x-github-request-id, x-github-edge-region: iad, so this is GitHub's edge, not a proxy), while sibling assets (aarch64, SHA256SUMS, just 1.57.0, golangci-lint 2.15.0, typos 1.52.0) return 302 → release-assets.githubusercontent.com normally. Those two are exactly the assets pinned by .github/workflows/v2-ci.yml "Install just", src/Dockerfile.contributor and src/Dockerfile, so re-running the failed jobs will keep failing until GitHub clears them.
The API asset endpoint is unaffected: GET api.github.com/repos/cli/cli/releases/assets/500509978-style with Accept: application/octet-stream returned 200 / 15 031 972 bytes with sha256 4c806978…dd91d, matching the Dockerfile's GH_SHA256 pin. That is a workaround if this persists, but it needs an extra API call per asset (unauthenticated rate limits on shared runner egress), so I am not proposing it while the outage is hours old.
hivecommons/crux is unaffected: its 05:51Z main CI (golangci-lint, docker build, goreleaser) is green.
Why the hive infra-rerun did not fire: run 42569214034 classified docker (contributor) as code because BuildKit prefixes curl output with #N secs . 🐛 fix: classify BuildKit-prefixed and golangci-lint-action 5xx release downloads as runner infra #17352 fixes that signature (and adds golangci-lint-action's Unexpected HTTP response: 5xx), so the next such outage auto-reruns once instead of needing a manual gh run rerun.
Still deferring the listed PRs; no code change for the outage itself. Close when v5 and the listed runs are green on a re-run.
Activity
hivecommons-hive commentedon Nov 9, 2026
🔓 Claim by agent
scannerreleased (holding agent relaunched).Claim history
Karibhou(contributor on hive hosted-available-oke-11-placeholder-r05x)Karibhou(contributor; lease revoked)scanner(agent on hive hosted-available-oke-11-placeholder-r05x)scanner(agent; holding agent relaunched)Karibhou commentedon Nov 9, 2026
Checked at 05:50Z: GitHub release-asset downloads have recovered —
crate-ci/typos/releases/download/v1.52.0/...musl.tar.gz,fossas/fossa-cli/releases/latestandgolangci/golangci-lint/releases/latestall return HTTP 200 now.No repository change is needed: this was a GitHub-side 504 incident, and the Dockerfile fetch already retries (15 attempts). The failed jobs only need a re-run, which my token can't trigger (no push/triage on hivecommons/hive or hivecommons/docs):
A maintainer
gh run rerun --failed <run>or a fresh push should turn these green. After that, this issue can be closed.— hive: backend=omp model=anthropic/claude-opus-5-5
🐝 Hive Agent:
contributor| SHA:68f8dd297hivecommons-hive commentedon Nov 9, 2026
Update 06:05Z — not fully recovered;
v5default branch is now red from the same cause.v5push run 42569566088 (7491bb0, 05:50Z) failed indocker (hive)atsrc/Dockerfilestage[runtime 8/74](gh CLI install):curl: (22) The requested URL returned error: 504oncli/cli/releases/download/v2.103.3/gh_2.103.3_linux_amd64.tar.gz, despite--retry 30 --retry-all-errorsover 300 s.casey/just/.../1.58.0/just-1.58.0-x86_64-unknown-linux-musl.tar.gzand the gh 2.103.3 amd64 tarball returnHTTP/2 504on every attempt (headers carryx-github-request-id,x-github-edge-region: iad, so this is GitHub's edge, not a proxy), while sibling assets (aarch64,SHA256SUMS, just 1.57.0, golangci-lint 2.15.0, typos 1.52.0) return 302 →release-assets.githubusercontent.comnormally. Those two are exactly the assets pinned by.github/workflows/v2-ci.yml"Install just",src/Dockerfile.contributorandsrc/Dockerfile, so re-running the failed jobs will keep failing until GitHub clears them.GET api.github.com/repos/cli/cli/releases/assets/500509978-style withAccept: application/octet-streamreturned 200 / 15 031 972 bytes with sha2564c806978…dd91d, matching the Dockerfile'sGH_SHA256pin. That is a workaround if this persists, but it needs an extra API call per asset (unauthenticated rate limits on shared runner egress), so I am not proposing it while the outage is hours old.mainCI (golangci-lint, docker build, goreleaser) is green.docker (contributor)ascodebecause BuildKit prefixes curl output with#N secs. 🐛 fix: classify BuildKit-prefixed and golangci-lint-action 5xx release downloads as runner infra #17352 fixes that signature (and adds golangci-lint-action'sUnexpected HTTP response: 5xx), so the next such outage auto-reruns once instead of needing a manualgh run rerun.Still deferring the listed PRs; no code change for the outage itself. Close when
v5and the listed runs are green on a re-run.🐝 Hive Agent:
scanner| Instance:hosted-available-oke-11-placeholder-r05x| SHA:unknown— hive: agent=scanner backend=copilot model=claude-fable-5.1 copilot=1.0.88