Repository navigation
CI: Magic Nix Cache throttling (HTTP 418) fails nix flake check without running it #774
Description
Problem
The nix flake check CI job intermittently fails for infrastructure reasons that have nothing to do with the change under test: the Magic Nix Cache backend throttles the runner (HTTP 418 rate-limit), the job dies before or during cache access, and NO check actually runs — but the PR shows a failed check. Sweeps then cannot certify a merge from CI, and a re-run (which passes) costs a full queue cycle.
Evidence
- 2026-10-24, PR fix(id-web): detect .pm.json compound extension case-insensitively #771 (fix for id(web): detect_mode's .pm.json check is case-sensitive — document.PM.JSON opens Raw instead of Rich (and downloads as doc.PM.JSON.pm.json) #770), flake check attempt 1: failed with Magic Nix Cache throttle / rate-limit 418; no check executed. Remaining checks (treefmt, eval, run, CodeRabbit) passed; the PR was left open pending a re-run purely because of this.
- 2026-10-24, PR fix(id): let a max-size image fit the upload route's body limit #747: post-merge flake check on the final head likewise unconfirmed due to the same infra throttling pattern.
- Pattern in both cases: the failure is in cache access, not in any derivation the PR touches; a later re-run of the identical head passes.
Why it matters
- The four-repo sweeps merge on green checks (Drew's standing directive: merge good PRs, fix later if needed). A cache-service hiccup masquerading as a red check either blocks good merges or trains everyone to ignore red checks — both bad.
- It burns the scarcest resource in this system, verified-merge windows, on re-runs of identical heads.
Asks
- Make cache-layer failures non-fatal to the check verdict: if the cache backend is unreachable or throttling (418/5xx on cache access), the job should fall back to building without the cache (or retry with backoff) and its pass/fail should reflect the code, not the cache service. E.g.
continue-on-erroron the cache step, or the DeterminateSystems action's failure-mode settings if it offers one. - Evaluate moving the flake check's cache to a backend this project controls — Cachix is already wired into the fleet's local nix config (omnibin substituter) — or GitHub's own actions cache, so CI health does not depend on a free-tier third-party cache's rate limits.
- Secondary, observed during sweep work on this repo:
gh pr checkshas been seen exiting 0 while a check job in the same PR had failed. Worth a look while in here — a checks summary that can say green over a red job compounds the trust problem above.
Acceptance criteria
- A PR whose only flake-check failure is a cache-backend 418/5xx either passes on the cache-less fallback or is reported distinctly as infra-failed (not code-failed), without a manual re-run.
- The cache backend choice for the flake check is recorded in the workflow (or an ADR/comment) with the throttling history as the reason.
Related: #375 (DeterminateSystems actions floated on @main in 6 workflows — same action family), #257 (CI disk space, different failure mode).
Metadata
Metadata
Assignees
Labels
CI/CD pipelines, workflows, and build automation (area)Medium: expected under 1 day of workCI/CD pipelines, workflows, and build automationIntake review done: acceptance criteria, links, and normalized labels addedOrdinary priority (the default)Filed by the new-issue-creator jobQueue packet kind: investigate a CI failureQueue packet kind: verify, reproduce, and route this item
Activity
developing-today commentedon Oct 24, 2026
CODE-110
dezren39 commentedon Oct 24, 2026
Owner direction (Drew, 2026-10-24): simpler than fixing the cache — don't use nix for GitHub Actions. This repo already has the precedent: #286 replaced nix with direct toolchains in Actions. Preferred resolution for this issue is therefore to retire the
nix flake checkActions job in favor of direct-toolchain checks (cargo/bun/etc. as #286 did), not to nurse the Magic Nix Cache. The cache-fallback asks above only matter if a nix job has to stay in Actions for some specific check that cannot run any other way — if so, name that check here. Acceptance update: this closes when no Actions job depends on nix (or the exceptions are named and their cache failures are non-fatal per the original asks).ci(id): run shard logic from a script file, not a just shebang recipe (…
dezren39 commentedon Oct 26, 2026
Intake review
Still live: no merged PR since 2026-10-24 records a cache-failure fallback, a backend change, or a recorded cache-backend decision for the flake check, and the issue's two documented 418 incidents (PRs #771, #747) stand unaddressed. Acceptance criteria were already present, so the body is unchanged. (No source/* label applied: the filer is not recorded in the body — the evidence mixes pr-review and sweep observations.)
Related: #257 (CI ENOSPC — different failure mode, same 'CI verdict does not reflect the code' theme; note #257's investigation found the PR gate has since been matrix-split per check, which changes where a cache fallback would live), #375 (same DeterminateSystems action family floated on @main).
Notes / risks: ask 3 (the
gh pr checksexit-0-over-a-red-job observation) is a secondary, separable thread — it should not block the cache-fallback work. Any backend switch (ask 2) is a cost/control decision the criteria correctly frame as needing a recorded rationale.Suggested approach: first make cache-step failure non-fatal with a cache-less fallback on the flake-check workflow (ask 1, the criteria's core), then record the backend decision; verify by simulating a cache outage on a test PR if the workflow supports it.
Labels normalized by the fleet monitor: kind/ci, status/needs-triage, priority/normal, effort/m, area/ci, meta/enriched (task/ci-investigation was already present).
44 remaining items
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 4, 2026
🤖 Agent note · picked up
Merge pull request #5259 from developing-today/queue/8049-774-nix-cac…
dezren39 commentedon Nov 4, 2026
agent-note:v1
state: done (fixed_merged)
queue: repo-health-code-pilot
task: 8049, worker repo-worker-code, lane bf419306-c4ef-470f-a553-beabf93239de
at: 2026-11-04T03:11:08Z
result: PR #5259 merged as 9bd87e6. All eight residual cache steps are best-effort; the backend migration remains outside this task.