Wire M10.7b interpolation and the stale loss view into the client
Foundation / checks (deploy) (push) Successful in 5s
Foundation / checks (ecs) (push) Successful in 1m55s
Foundation / checks (client) (push) Successful in 12m27s
Foundation / checks (network) (push) Successful in 12m46s
Foundation / checks (tsan) (push) Successful in 7m59s
Foundation / postgres-tools (push) Canceled after 0s
Foundation / server-image (push) Canceled after 0s
Foundation / image (push) Canceled after 0s
Foundation / checks (checks) (push) Canceled after 25m13s
Foundation / checks (postgres) (push) Canceled after 12m48s

ADR-0095. The engineering client times presentation with the tick clock:
its own marker between ticks, other markers interpolated a few ticks behind
(grey when stale). Silence beyond 3 ticks and long-gap holds are stale. A lost
session leaves its last view frozen and labelled stale until the reconnect's
fresh baseline; nothing is predicted or sent meanwhile.

evo-motion-trace --remote measures remote-marker error between two clients
through the relay, with a 1.5 s outage (motion-trace-remote-smoke CTest).
Prediction errors are recorded only for ticks inputs are scheduled for.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
dingo
2026-10-06 17:50:41 -04:00
co-authored by Claude Opus 5.5
parent 90cdb61e30
commit 5728e7682e
17 changed files with 651 additions and 210 deletions
+44
View File
@@ -4635,3 +4635,47 @@ Executed:
- `client-network`: 13/13.
Not done: client wiring, the loss view and the two-client trace (10.7b).
## 2026-10-06 — M10.7b client interpolation, loss view and traces (ADR-0095)
Implemented:
- the engineering client's tick clock, interpolated remote markers (grey when stale), the
own marker between ticks, and the frozen stale view on loss (banner, all markers stale,
own marker at its last authoritative position), reset on Welcome;
- `TickClock::silence` and silence-based staleness; long-gap holds marked stale;
- error recording limited to scheduled ticks (`predict_between(..., record)`);
- `evo-motion-trace --remote` and the CTest `motion-trace-remote-smoke`;
- a shared region bench in the trace tool.
Found and fixed during development:
- an outage never showed stale (the frozen clock kept the render tick inside the buffer);
- post-outage holds were shown as current;
- false prediction errors from presenting one tick past the scheduled ticks (a Windows-only
`client-remote-session` failure);
- MSVC rejecting `std::erase_if` with a member-pointer predicate;
- two clang-tidy optional-access findings.
Figures are in docs/networking/M10_PREDICTION_TRACES.md:
- remote markers shown as current: p99 at most 60.7 mm, max 100 mm;
- outages: 84-90 % of samples shown stale, recovery 150-950 ms;
- smoke variance: one of three runs had 32 % extrapolated and 36 % stale samples, with
current errors still 0.
Executed:
- **Linux GCC 14:**
- preset `client-network`: CTest 16/16 (including both trace smokes and
client-remote-session);
- preset `quic`: 4/4;
- full remote and prediction trace runs.
- **Linux Clang 19:** ASan/UBSan `evo-network-tests`, and clang-tidy 19 on the trace tool,
client app, panels, remote test, interpolation sources and tests.
- **Windows MSVC 19.44** (fresh binaries):
- preset `client-network`: 14/14;
- `client-remote-session` passed 5 times in a row after the fix;
- preset `quic`: 4/4.
The Postgres suite was not rerun: no server code changed in M10.7.
Not done:
- interpolating organisms (none move);
- a GUI run against evolution-dev (needs a v3 server).