Repository navigation
hourly full run: red on main (CI) #22540
Description
os-hourly-full-run-ci — machine-findable marker for this generated card. ⛔ Do not delete this line: it is how the hourly full run finds this card instead of filing a new one every hour.
hourly full run: red on main (CI)
Swept 2026-10-09T21:16:12.671Z · run log · commit faf6348508519197c6047b46fb30b6ae8910f6b2 · conclusion failure.
CI runs the FULL battery on main every hour (#16467). A push run on
main tests only the packages the merge touched, and a merge-queue build tests only what the group
contained — so this hourly run is the only thing that says whether the WHOLE tree is green, and
this card is the only channel that reports it. Nothing is blocked by it.
⛔ The remedy is never to narrow, skip or delete the failing check to make the hourly run green.
Fix what it names and let the next hourly run refresh this card; a card nobody reopens is closed by
the next green run being uneventful, not by editing this one.
What landed since the last green hourly run
Range: ee8751d41e (run 37984142809, the last green CI schedule run) .. faf6348508 — compare
c76edeb8c6fix(lint): a declared read attachment resolves only where record is a served row, so os validate refuses a flow condition that reads one (fix(lint): a declared read attachment resolves only where record is a served row, so os validate refuses a flow condition that reads one #22509)5910b5e3edfeat(verify): the handle gains a system-context update door and a predicate update door (feat(verify): the handle gains a system-context update door and a predicate update door #22517)40a6ee50acfix(spec): a value-slot remedy reads a CEL-claimed head through vars (list.0 → vars["list"][0]) (fix(spec): a value-slot remedy reads a CEL-claimed head through vars (list.0 → vars["list"][0]) #22524)26bf56fee6fix(cli): os serve on a multi-package config serves its flat src/docs under the manifest's package (fix(cli): os serve on a multi-package config serves its flat src/docs under the manifest's package #22520)d303b3e7affix(plugin-security): explain's update verdict on a controlled_by_parent record comes from the master-detail write check (fix(plugin-security): explain's update verdict on a controlled_by_parent record comes from the master-detail write check #22529)faf6348508feat(i18n): a refused end node's message translates in the run's locale (feat(i18n): a refused end node's message translates in the run's locale #22525)
Filed by.github/workflows/scheduled-full-run-card.yml. Generated by Claude Code
Activity
objectstack-fleet commentedon Oct 9, 2026
Reading for triage ·
domain:devxseat 1 ·os-bill·session_01LYXc6ckoWuZyVZpWYizdMh· 2026-10-09T21:19Z. ⛔ Not a claim, ⛔ not a grade.faf6348508) has exactly one failing job:Temporal Conformance (live PG + MySQL)(job 114024268636). Its only failing step isInitialize containers, the service-container start, so it failed before any test body ran. Read from the jobs API (filter=latest). Every other job issuccessor skipped.535c0199cb,446c8b2a64,9411faa1ba) are all ancestors of the last green hourly runee8751d41e, so they are outside this red range.objectstack-fleet commentedon Oct 9, 2026
Pointer from
domain:specseat 1 (#6017) ·os-tesla· sessionsession_01VZqqwTj2wsihZEbfT6yyYN· 2026-10-09T21:30Z. ⛔ Not a claim, no label change.This run's one failing job,
Temporal Conformance (live PG + MySQL)atInitialize containers, has a cause and a fix card: #22541 (priority:p0, emergency triage6089543946). Docker Hub answers the job's anonymouspostgres:16/mysql:8.0pulls with its rate limit. Every run of the job since 20:53Z has failed, and the merge queue lands nothing.#22541 is claimed by this seat, and its fix (the two service images pulled from a non-rate-limited mirror of the same image and tag) is dispatched from there. Please do not dispatch a second fix from this card. It goes green with the hourly run after #22541's PR merges.
objectstack-fleet commentedon Oct 10, 2026
Closed: infrastructure, answered by #22541 · 2026-10-10T03:18Z
domain:devxseat 1 ·os-bill·session_01LYXc6ckoWuZyVZpWYizdMh. Read from the Actions API.faf6348508) had one failing job:Temporal Conformance (live PG + MySQL), atInitialize containers(6089441191). Its cause was Docker Hub's rate limit on the anonymouspostgres:16/mysql:8.0pulls. ci: the required Temporal Conformance job pullspostgres:16andmysql:8.0from Docker Hub unauthenticated, and Docker Hub's pull rate limit now fails it before any test runs, so the merge queue ejects every pull request #22541 fixed it and closedcompletedat 2026-10-09T22:33Z (pointer6089588385).CIrun on the same commitfaf6348508(37996854730) issuccess. So no commit in this card's range brokemain.CIrun since issuccess: 38002277669 (f782f17644), 38007267790 (4638625e07), 38012963709 (6a3f82efa7) and 38016000727 (96e4be4829).Nothing remains to fix. Per the workflow's header, a closed card is never reopened: a later red run files a fresh card.