M11-PT-001: read v10 perceptions from servers built before the bud cost
Foundation / checks (ecs) (push) Successful in 2m16s
Foundation / checks (deploy) (push) Successful in 4m4s
Foundation / checks (tsan) (push) Successful in 11m42s
Foundation / checks (network) (push) Successful in 19m59s
Foundation / checks (client) (push) Successful in 21m12s
Foundation / checks (checks) (push) Successful in 46m11s
Foundation / checks (postgres) (push) Successful in 46m18s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Successful in 3m12s
Foundation / image (push) Successful in 3m28s
Foundation / checks (ecs) (push) Successful in 2m16s
Foundation / checks (deploy) (push) Successful in 4m4s
Foundation / checks (tsan) (push) Successful in 11m42s
Foundation / checks (network) (push) Successful in 19m59s
Foundation / checks (client) (push) Successful in 21m12s
Foundation / checks (checks) (push) Successful in 46m11s
Foundation / checks (postgres) (push) Successful in 46m18s
Foundation / postgres-tools (push) Successful in 28s
Foundation / server-image (push) Successful in 3m12s
Foundation / image (push) Successful in 3m28s
The bud cost (d98d71e) grew the v10 cellular perception prefix from 82 to 122 bytes
without a version bump. A rebuilt client connected to the live DEV region (server
3e5b8cef, older) refused every perception as wrong_length, closed the session as a
protocol error and reconnected; each reconnect's birth request answered existing_life
and no view ever arrived ("Existing cell is already bound to this account").
The decoder now also accepts the earlier v10 layout, with no bud cost. The two lengths
never coincide (40 bytes is not a whole 48-byte patch). The client already hides a zero
bud cost.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
@@ -60,6 +60,28 @@ No deployment, database mutation or runtime fix was performed for this note.
|
||||
`kubectl config current-context` reports that no current context is set in this
|
||||
workspace, so live DEV logs/state were unavailable for confirming these candidates.
|
||||
|
||||
### Follow-up diagnosis (2026-10-16, region 5)
|
||||
|
||||
The retest reproduced the message against live region 5. Read-only checks showed:
|
||||
|
||||
- The life was born and active: `living owned=1`, `lingering=0`, `suspended=0`, and the
|
||||
reservation was open, born at tick 1.
|
||||
- Later relaunches only added refused birth requests.
|
||||
|
||||
So neither placement nor resume was blocking. The cause was a wire mismatch:
|
||||
|
||||
- The live server image (`3e5b8cef…`) predates the bud-cost change (d98d71e). That change
|
||||
grew the v10 perception prefix from 82 to 122 bytes without a version bump.
|
||||
- A rebuilt client therefore refused every perception as `wrong_length`, closed the
|
||||
session as a protocol error and reconnected.
|
||||
- On each reconnect the birth request got `existing_life` again, and no view ever arrived.
|
||||
|
||||
The decoder now also accepts the earlier v10 layout, which carries no bud cost. The two
|
||||
lengths can never coincide, because 40 bytes is not a whole 48-byte patch.
|
||||
|
||||
This explains the reproduced case only. The first report predates d98d71e, and its
|
||||
cause remains unconfirmed.
|
||||
|
||||
## Retest backlog
|
||||
|
||||
| Local issue | Priority / scope | Acceptance evidence |
|
||||
|
||||
Reference in New Issue
Block a user