Record cellular births in replay traces
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (checks) (push) Failing after 39s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (postgres) (push) Failing after 52s
Foundation / checks (tsan) (push) Failing after 33s
Foundation / checks (network) (push) Failing after 3m4s
Foundation / checks (client) (push) Failing after 4m22s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Foundation / checks (deploy) (push) Successful in 6s
Foundation / checks (checks) (push) Failing after 39s
Foundation / checks (ecs) (push) Successful in 2m0s
Foundation / checks (postgres) (push) Failing after 52s
Foundation / checks (tsan) (push) Failing after 33s
Foundation / checks (network) (push) Failing after 3m4s
Foundation / checks (client) (push) Failing after 4m22s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
This commit is contained in:
@@ -45,3 +45,12 @@ deterministic and bounded, while the complete post-tick checkpoint remains the
|
||||
authoritative recovery state. Profile 1–3 trace formats and manifest size rules
|
||||
remain unchanged. Process-level uncertain-commit and restart tests are still
|
||||
required before M11.3d can close.
|
||||
|
||||
ADR-0114 extends the profile-4 trace to format 2. It retains the 112-byte
|
||||
header and per-tick life intentions, then records a bounded birth set sorted by
|
||||
account and request. Each birth record is 40 bytes: account (16 bytes), request
|
||||
ID, control generation, and allocator-issued identity (u64 LE each). The birth
|
||||
is replayed after that tick's existing-life step. Format-1 traces remain
|
||||
decodable for already committed checkpoints. The new maximum is
|
||||
`112 + ticks * (8 + 256 * (24 + 40))` bytes; migration 22 adjusts the profile-4
|
||||
manifest bound without changing other profiles.
|
||||
|
||||
@@ -310,6 +310,14 @@ scoped change before starting the next segment.
|
||||
following tick. This remains in-memory: canonical birth trace, durable
|
||||
publication/recovery and session scheduling remain open, so 11.3e is not
|
||||
playable yet.
|
||||
- 11.3d-7h: profile-4 replay trace format 2 adds canonically ordered bounded
|
||||
birth records after each tick's existing-life intentions. Replay applies each
|
||||
birth at the end tick, derives all biology and placement from the predecessor,
|
||||
and verifies that request identity, generation and allocator identity are
|
||||
nonzero and unique. The decoder still accepts format-1 traces. C++ manifest
|
||||
validation and migration 22 raise the profile-4 trace ceiling; PostgreSQL and
|
||||
end-to-end birth publication tests are still pending, so this is not yet a
|
||||
durable birth path or a playable 11.3e slice.
|
||||
|
||||
## Exit boundary
|
||||
|
||||
|
||||
@@ -6398,3 +6398,22 @@ jobs remain stalled without output and do not count as validation. The current
|
||||
Windows environment also lacks `clang-format`. Durable birth trace and server
|
||||
integration remain unimplemented, so this does not make the cellular stage
|
||||
playable.
|
||||
|
||||
## 2026-10-11 — M11.3d-7h cellular birth replay trace (database pending)
|
||||
|
||||
Profile-4 cellular trace format 2 now records a bounded birth set after each
|
||||
tick's existing-life intentions. Recovery deterministically applies births at
|
||||
the end tick, and the decoder retains format-1 support for old committed traces.
|
||||
The C++ manifest bound was expanded; migration 22 updates the PostgreSQL
|
||||
profile-4 trace ceiling and the migration runner/CI history checks.
|
||||
|
||||
The focused lifecycle test passes under GCC 13.2 in debug and `-DNDEBUG` builds,
|
||||
including trace encode/decode, version-1 decoding, funded end-of-tick birth
|
||||
replay, and malformed generation rejection. Strict-warning syntax compilation
|
||||
of `src/persistence/region_checkpoint.cpp` and `git diff --check` pass. This
|
||||
Windows environment has no `psql`, so migration execution and PostgreSQL
|
||||
integration are pending CI. CTest, sanitizer checks, clang-format and CI have
|
||||
not run for this segment. The Windows `bash.exe` shim is access-denied, and the
|
||||
migration test translation unit cannot compile here because its process fixture
|
||||
requires POSIX `poll.h`. The previously noted unrelated initializer warning in
|
||||
`cellular_region_step.cpp:29` is demoted only for the manual focused test build.
|
||||
|
||||
Reference in New Issue
Block a user