Carry bud actions and the v5 bundle through protocol and persistence
Foundation / checks (ecs) (push) Successful in 2m30s
Foundation / checks (deploy) (push) Successful in 4m0s
Foundation / checks (tsan) (push) Successful in 10m37s
Foundation / checks (client) (push) Failing after 13m56s
Foundation / checks (network) (push) Successful in 19m9s
Foundation / checks (checks) (push) Successful in 42m54s
Foundation / checks (postgres) (push) Successful in 44m9s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
Foundation / checks (ecs) (push) Successful in 2m30s
Foundation / checks (deploy) (push) Successful in 4m0s
Foundation / checks (tsan) (push) Successful in 10m37s
Foundation / checks (client) (push) Failing after 13m56s
Foundation / checks (network) (push) Successful in 19m9s
Foundation / checks (checks) (push) Successful in 42m54s
Foundation / checks (postgres) (push) Successful in 44m9s
Foundation / postgres-tools (push) Skipped
Foundation / server-image (push) Skipped
Foundation / image (push) Skipped
M11.5c (ADR-0125): v10 cellular actions, the canonical input and the trace carry target kind 3 (bud), matched to durable actions; below rules 4 the owner ignores it. The v5 version bundle is admitted in C++ and by schema v36, which also admits kind 3 in SQL action inputs; the provisioner offers cellular-v3. A PostgreSQL test publishes a bud from a fed founder and recovers it after a host restart. The publication tests now use commit ids no other suite produces. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -49,7 +49,7 @@ descendant, and no special wildlife biology.
|
||||
channel (abundant energy never pays for matter), partial growth, damage and a
|
||||
genome without the capability.
|
||||
- 11.5b: owner format 5 / rules 4 (`CellularLivesProfile::budding`). A
|
||||
`CellularStepIntent::bud` (rules 4 only, exclusive with feeding and
|
||||
`CellularStepIntent::bud` (ignored below rules 4, exclusive with feeding and
|
||||
engulfing) funds a bud after the tick's mutations through `fund_bud`, places
|
||||
it touching the parent (eight fixed directions), gives it the next
|
||||
region-namespace identity and the parent's current genome, and records its
|
||||
@@ -58,4 +58,13 @@ descendant, and no special wildlife biology.
|
||||
offers. Validation and restore enforce the identity namespace and sequence;
|
||||
`cellular-lives-owner` buds a fed founder, checks the refusals spend nothing,
|
||||
conservation, the shared genome's two carriers, wildlife feeding without
|
||||
offers, exact restore and a rewound sequence; rules 3 refuses a bud intent.
|
||||
offers, exact restore and a rewound sequence; rules 3 ignores a bud intent.
|
||||
- 11.5c: v10 cellular actions and the canonical input carry target kind 3
|
||||
(bud, zero coordinates, exclusive with intake and engulfment); the trace keeps
|
||||
it as an intention byte and the action matcher compares it. Below rules 4 the
|
||||
owner ignores it. The v5 version bundle (`{4,5,1,1,1,2,1,2,1}`, revision
|
||||
history) is admitted in C++ and by schema v36, which also admits kind 3 in SQL
|
||||
action inputs and the v5 bundle for format-3 birth traces. The provisioner
|
||||
offers `cellular-v3` (rules 4). A rules-4 owner refuses founder identities at
|
||||
or above 2^63; the allocator keeps its full range. PostgreSQL tests publish a
|
||||
real bud from a fed founder, restart the host and recover the wildlife cell.
|
||||
|
||||
@@ -7363,3 +7363,30 @@ refusal of a bud intent.
|
||||
|
||||
Executed locally: MSVC Debug `ctest` 69/69; g++-14 `-Werror`, clang-tidy-19 and
|
||||
clang-format 19.1.5 on the owner, region step and owner tests.
|
||||
|
||||
## 2026-10-14 — CI run 372 PostgreSQL failure and fix; M11.5c bud action and v5 bundle
|
||||
|
||||
Run 372 (187b1a7, M11.4c) failed only `checks (postgres)`: the M11.4c-1
|
||||
publication test's first 64-tick feeding publish was refused client-side. The
|
||||
PostgreSQL adapter bounded every parameter to 4 KiB of text (ADR-0059), and a
|
||||
cellular trace is sent as one hex `bytea` parameter, so any trace over about
|
||||
2 KiB failed as `bounds` and surfaced as `invalid`. A one-tick trace crosses that
|
||||
at about 85 lives, which budding makes reachable. ADR-0126 raises the bound to
|
||||
4 MiB, enough for the largest admitted trace. The same run would then have
|
||||
failed on test commit ids: the new publication tests used uniform-byte commit
|
||||
ids (`0x60`, `0x65`) that other suites also produce; they now use mixed bytes.
|
||||
|
||||
M11.5c adds bud target kind 3 (v10 actions, canonical input, trace intention,
|
||||
action matching), the v5 bundle, schema v36 (kind 3 in SQL inputs, v5 bundle
|
||||
normalization and birth binding), the `cellular-v3` provisioner opening, and
|
||||
tests: protocol and canonical-input kind 3, session batch and trace round trip,
|
||||
v5 checkpoint restore, v36 SQL checks, `cellular-v3` provisioning, and a
|
||||
PostgreSQL bud publication with host restart and recovery.
|
||||
|
||||
Executed locally: `postgres-check.sh --full` (WSL g++-14 Release: C++ suite, life
|
||||
reservations, backup, DR, upgrade, migration history, permission audit and checksum
|
||||
drift; 489 s) passes; before that the C++ suite (`postgres-check.sh
|
||||
--suite-only`, WSL g++-14 Release) passes, including the M11.4c-1/-2 and M11.5
|
||||
publication tests; MSVC Debug 69/69, network 75/75, client-network 89/89 (the
|
||||
two motion-trace smokes needed a serial rerun under load); g++-14 `-Werror`,
|
||||
clang-tidy-19 (no new findings) and clang-format 19.1.5 on the changed sources.
|
||||
|
||||
Reference in New Issue
Block a user