Fix cellular action tick publication offset
Foundation / checks (checks) (push) Successful in 6s
Foundation / checks (client) (push) Successful in 4s
Foundation / checks (ecs) (push) Successful in 5s
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (network) (push) Successful in 5s
Foundation / checks (tsan) (push) Successful in 5s
Foundation / checks (postgres) (push) Failing after 32m57s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped

This commit is contained in:
dingo
2026-10-12 06:42:09 -04:00
parent 3fa53d8ee6
commit fa5a9afeff
5 changed files with 108 additions and 8 deletions
+10
View File
@@ -7142,3 +7142,13 @@ record. The server-image path selector did not include
server image from this commit. The selector now includes that integration test;
CI must confirm both the server-image build and Harbor publication. Harbor
publishing also requires the `HARBOR_SERVER_REPOSITORY` repository variable.
CI run #336 fixed the build selector and ran the PostgreSQL publication test,
which exposed an off-by-one in migration 20: `manifest_uint` reads from a
zero-based offset, but the publisher supplied 25 instead of 24 for each
canonical action tick. This made the durable tick disagree with the 24-byte
input, so PostgreSQL correctly rejected the action row. Migration 33 replaces
the publisher with the corrected offset while retaining migration 20's recorded
checksum. The migration runner's accepted latest history and upgrade fixtures
now extend through version 33. Local PostgreSQL is unavailable on this Windows
environment; migration, publication, and server-image checks are awaiting CI.