Guard PostgreSQL row parser optionals
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (checks) (push) Failing after 4m3s
Foundation / checks (client) (push) Successful in 13m10s
Foundation / checks (network) (push) Successful in 15m10s
Foundation / checks (tsan) (push) Successful in 8m20s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (postgres) (push) Canceled after 21m43s

This commit is contained in:
dingo
2026-10-11 13:08:33 -04:00
parent 16d8a9d098
commit 6d60a7f285
2 changed files with 23 additions and 14 deletions
+8
View File
@@ -6927,3 +6927,11 @@ optional in the PostgreSQL reservation-row decoder at
empty-string default to the hex parser; absent or malformed input still fails
the existing validation path. The PostgreSQL job failed on this diagnostic, so
the dependent server-image and Harbor jobs did not start.
CI run #292 confirmed the reservation-input decoder repair, then clang analysis
reported additional optional-value and ineffective-move warnings in
`src/persistence/region_lease_store.cpp` while building the PostgreSQL target.
The affected action-record, migration-record, commit-status, publication-action,
and life-owner parsers now use safe optional defaults or checked copies; missing
mutation input retains its prior absent-value behavior. The PostgreSQL job failed
on these analyzer diagnostics, so the dependent image jobs did not start.