Validate clone provision frame before use
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m54s
Foundation / checks (checks) (push) Failing after 4m7s
Foundation / checks (tsan) (push) Canceled after 0s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (network) (push) Canceled after 3m54s
Foundation / checks (postgres) (push) Canceled after 1m49s
Foundation / checks (client) (push) Canceled after 5m58s

This commit is contained in:
dingo
2026-10-11 15:32:45 -04:00
parent 2518282ff0
commit 9ebbf844d0
2 changed files with 18 additions and 6 deletions
+9
View File
@@ -6955,3 +6955,12 @@ 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.
CI run #296 confirmed the action-ledger repair, then PostgreSQL analysis rejected
an unchecked `Options::primitive_frame` access in `apps/evo-world-clone/main.cpp`
while compiling the primitive-region provisioning path. The provision command now
uses a validated frame value for primitive and cellular openings. The default
Windows debug preset has PostgreSQL disabled and does not contain this target;
`clang-format` is also unavailable in the local environment, so PostgreSQL
analysis, format and integration checks remain delegated to CI. Run #297 must
confirm the fix and proceed through the server image and Harbor publication gates.