Send a life identity on the wire only with a born outcome
Foundation / checks (checks) (push) Successful in 40m57s
Foundation / checks (deploy) (push) Successful in 3m59s
Foundation / checks (ecs) (push) Successful in 2m19s
Foundation / checks (network) (push) Successful in 19m0s
Foundation / checks (postgres) (push) Successful in 43m16s
Foundation / checks (tsan) (push) Successful in 9m41s
Foundation / checks (client) (push) Successful in 13m43s
Foundation / postgres-tools (push) Successful in 18s
Foundation / server-image (push) Successful in 3m0s
Foundation / image (push) Successful in 3m15s

A fresh client launch sends a new birth request. For an account that
already has a cell, the cellular host reports existing_life with the
reserved identity, and RegionSessions forwarded it although the codec
accepts an identity only with born. The client closed with protocol and
retried with the next grant until the account was rate-limited, so no
account with a cell could log in from a new launch. Clear the identity
and commit on every other result at the session boundary, and test that
an existing_life refusal arrives valid while the session stays open.

The client now names the cause of a protocol close on stderr, which is
how this was found. Record it in ADR-0123. Also refresh the dev session
window (3 h).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-13 16:51:09 -04:00
co-authored by Claude Opus 5.5
parent f3aecaf36a
commit e9b010ed01
6 changed files with 68 additions and 11 deletions
@@ -96,6 +96,15 @@ region in DEV. Bringing one up exposed four gaps:
- Other births stay queued until the account returns.
- Restarting the pod cleared the in-memory queue. The reservation is
durable, and the client's query re-queues it.
- **A refused life request no longer breaks the session.** The cellular host
reports the reserved identity on a pending or refused request.
`RegionSessions` forwarded it unchanged, and the codec rejects any identity
or commit on a non-born outcome. The client closed with `protocol` and
retried with the next grant until the account was rate-limited. The client
picks a new birth request per launch, so every account that already had a
cell was refused as `existing_life` and could not log in from a fresh
launch. The session layer now sends the identity and commit only with
`born`.
- **Grants for region 3 must be minted with `--region 3 --lifetime 300` or
less.** Longer probe sessions require a separate, reviewed change to the
cellular grant ceiling; this ADR does not make it.
+13 -1
View File
@@ -7194,4 +7194,16 @@ failed again every 20 s, refusing logins with `shutdown`. A restart of
`Deployment/evo-region` (permitted by the agent contract) cleared the
in-memory queue, and the region held `ready 1` at epoch 8 from 20:20:44 UTC.
`serve_cellular` now includes, and ticks for, only births whose account holds
a session. Checked locally: g++-14 `-Werror`, clang-tidy-19 and clang-format.
a session. Checked locally: g++-14 `-Werror`, clang-tidy-19 and clang-format.
Logins from a fresh client launch then failed in a loop: welcome, then the
client closed with `protocol`. A diagnostic in `RegionSessionClient` (now
kept: protocol closes name their cause on stderr) showed
`message decode detail=6 bytes=33`, a primitive-life outcome the codec
rejects. A new client launch sends a new birth request; for an account that
already has a cell, the cellular host reports `existing_life` with the
reserved identity, and `RegionSessions` forwarded it although the codec allows
an identity only with `born`. The session layer now clears identity and commit
on every other result. `quic_sessions` adds an `existing_life` refusal that
must arrive valid while the session stays established. Locally (MSVC, client
preset) the case failed with the same 33-byte decode error before the fix and
passed after it.