Guard PostgreSQL action ledger optionals
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m52s
Foundation / checks (client) (push) Successful in 13m36s
Foundation / checks (network) (push) Successful in 14m54s
Foundation / checks (tsan) (push) Successful in 8m22s
Foundation / checks (postgres) (push) Failing after 23m23s
Foundation / checks (checks) (push) Successful in 37m42s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-11 14:53:32 -04:00
parent 8a9a318d78
commit 2518282ff0
2 changed files with 11 additions and 4 deletions
+7
View File
@@ -6948,3 +6948,10 @@ plus an intentionally best-effort lease release expressed as a discarded value.
The image jobs were skipped because that matrix job failed. The host now passes
safe grant/outcome values after presence checks and captures the shutdown release
result using the existing RegionHost convention.
CI run #295 passed the main checks matrix, including the full cellular host build,
but PostgreSQL analysis next found checked-optional and ineffective-move warnings
in `src/server/session/postgres_action_ledger.cpp`. The single and batched
lookups now copy present rows via `value_or`, and the small durable result records
are copied without ineffective `std::move`. The PostgreSQL job failed on these
new diagnostics, so image publication remained skipped.