Add M10.4b durable action records (schema v11)
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m47s
Foundation / checks (network) (push) Successful in 9m30s
Foundation / checks (client) (push) Successful in 12m19s
Foundation / checks (tsan) (push) Successful in 7m43s
Foundation / checks (checks) (push) Successful in 31m29s
Foundation / checks (postgres) (push) Successful in 36m39s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 2m15s
Foundation / server-image (push) Successful in 20m37s
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m47s
Foundation / checks (network) (push) Successful in 9m30s
Foundation / checks (client) (push) Successful in 12m19s
Foundation / checks (tsan) (push) Successful in 7m43s
Foundation / checks (checks) (push) Successful in 31m29s
Foundation / checks (postgres) (push) Successful in 36m39s
Foundation / postgres-tools (push) Successful in 19s
Foundation / image (push) Successful in 2m15s
Foundation / server-image (push) Successful in 20m37s
Each batch's actions are recorded in the same statement as its checkpoint: one region_actions row per (world, account, action id) and the block in an append-only table, compared on exact retries and resolution. The region host attaches actions to the ticks they ride and reports acknowledgements and drops, keeping unknown-outcome batches unresolved. Outcomes come from the durable record via ActionLedger, so crashes before or after a commit, unknown publications and cross-region moves all resolve to one answer; a repeated id keeps its first record instead of stalling a region. ADR-0092. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -190,6 +190,16 @@ renewal requires the same generation, region and epoch and an unexpired control
|
||||
(`EVL12` otherwise). The privilege audit includes all three functions. Lock order: upgrade
|
||||
lock (shared), region lease row, account control row.
|
||||
|
||||
## Action records (schema v11, ADR-0092)
|
||||
|
||||
`publish_region_checkpoint(manifest, decisions, actions)` records a batch's action block
|
||||
([region-actions-v1](../../schemas/region-actions-v1.md)) in the same statement as its
|
||||
checkpoint: one `evolution.region_actions` row per new (world, account, action id), and the
|
||||
block in the append-only `region_commit_actions` (committed history itself is never
|
||||
updated). Exact retries and `resolve_region_commit(..., actions)` compare the block.
|
||||
`find_region_action` reads one record under the caller's exact region lease. The privilege
|
||||
audit covers all three functions; the tables and `check_action_block` are owner-only.
|
||||
|
||||
## Host lease discipline
|
||||
|
||||
Hosts use `LeaseAuthority` with `LeasePolicy` defaults: 20 s lease, 5 s renewal
|
||||
|
||||
Reference in New Issue
Block a user