Guard cellular profile migration recovery
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m53s
Foundation / checks (client) (push) Successful in 13m29s
Foundation / checks (network) (push) Successful in 14m48s
Foundation / checks (tsan) (push) Successful in 8m19s
Foundation / checks (postgres) (push) Failing after 20m2s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 34m44s

This commit is contained in:
dingo
2026-10-11 11:58:15 -04:00
parent 290c9501cd
commit 6a99d31b6e
2 changed files with 21 additions and 13 deletions
+7
View File
@@ -6913,3 +6913,10 @@ access at `src/persistence/cellular_checkpoint_store.cpp:550`: the stored action
block inside the successful database result. Recovery now validates that the
block is present and decodes a `value_or` copy. The PostgreSQL job failed on this
diagnostic, so this run also did not start server-image or Harbor publication.
CI run #290 confirmed both action-record repairs and found a third nested optional
access in the cellular profile-migration recovery check at
`src/persistence/cellular_checkpoint_store.cpp:464`. Recovery now copies the
optional migration record through `value_or` and validates the copy after
preserving the missing-record history failure. PostgreSQL failed on this
diagnostic, so the image and Harbor jobs remained blocked.