Skip to content

Keep the published record of a cell whose store was lost - #252

Merged
tamnd merged 3 commits into
mainfrom
keep-lost
Oct 10, 2026
Merged

tamnd merged 3 commits into
mainfrom
keep-lost

Conversation

@tamnd

@tamnd tamnd commented Oct 10, 2026

Copy link
Copy Markdown
Owner

server2's /var/tmp/gk was wiped this morning, including its result store. 1,542 of the 3,118 cells in matrix.json lived only there. Publishing from what's left would drop all of them and turn half the matrix back into holes.

gk publish now keeps the record it already published for any cell that no store has. The record keeps its square, and the class it was published with, until a newer run of the same coordinates takes over. --fresh drops such records, for when a cell was removed on purpose. Only the warning census and the configuration differential still read the cell directories, so they cover only the cells whose logs remain.

Most of those cells can come back from the last store mirror, sweep-2026-10-09-2215, which has everything except the build logs. This change is the safety net for anything the mirror doesn't have. Spec 10 notes the exception to "a result can always be traced to its cell directory".

A new test covers it. fmt, clippy and all 133 tests pass.

@tamnd tamnd added this to the G3: the legacy history milestone Oct 10, 2026
@tamnd tamnd added kind/feature New capability in gk or the pipeline area/results matrix.json, reports and publication priority/p1 Blocks the current milestone labels Oct 10, 2026
@tamnd
tamnd merged commit 6472e79 into main Oct 10, 2026
2 of 3 checks passed
@tamnd
tamnd deleted the keep-lost branch October 10, 2026 03:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/results matrix.json, reports and publication kind/feature New capability in gk or the pipeline priority/p1 Blocks the current milestone

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant