Merge remote-tracking branch 'origin/main' into stories/gev-stories

This commit is contained in:
Sameh Khamis committed 2026-11-16 14:28:09 -08:00
commit 56bd14d5f2
40 files changed
+909 -197

No files matched your search

+17 -14
View File
@@ -12,11 +12,13 @@ north.
While anything moves (a layer in motion, the camera, a followed contact), the
globe draws at the display's own refresh rate; there is no fixed 60 FPS cap.
The Cesium frame port (`src/render/cesium/ports.js`, its `idleFps`) caps a
parked scene at `IDLE_FRAME_RATE` (60, `src/renderGovernor.js`) ticks a
second while no hold is out, because Cesium still runs the clock, data sources
and update listeners on every animation frame even when it skips the draw; the
viewer starts at that cap until the frame port takes over. Through the idle
The render governor (`src/renderGovernor.js`) caps a parked scene at
`IDLE_FRAME_RATE` (60) ticks a second while nothing holds the loop, because
Cesium still runs the clock, data sources and update listeners on every
animation frame even when it skips the draw, and lifts the cap while anything
does: the frame port tells it when the loop's first hold is taken and its last
released, its own holds (animated visual styles) included. The viewer starts
at that cap until the governor is installed. Through the idle
render governor, the camera port holds continuous render from `moveStart` to `moveEnd`, and samples its
pose every 250 ms in between, so a camera drifting by rounding errors (no
`moveEnd`) is released after half a second at rest and held again if it moves. The world clock holds continuous render while
@@ -3996,10 +3998,10 @@ which embeds the MAP_KEY.
> a layer that needs no key, already holds one, or names a key the registry does
> not recognise. The earthquakes half
> still delivers in full. The shared loading reducer now treats an explicitly
> declared missing optional key as a configured terminal state rather than a
> failed multi-layer mission, so the global chip completes without showing
> `LOAD FAILED`. A genuine lifecycle or fetch failure still retains failure
> priority.
> declared missing optional key as its own terminal state rather than a
> failed multi-layer mission, so the global chip ends `KEY REQUIRED` (amber)
> instead of `LOAD FAILED`, on the first load and on every refresh. A genuine
> lifecycle or fetch failure still retains failure priority.
>
> **Acceptance changed with that ruling (2026-08-23).** `qa-firstrun` no longer
> asserts "a keyless Environmental never shows a failure chip" — that stopped
@@ -4691,12 +4693,13 @@ down | auth-failed` (plus the unchanged `missing-key`/`unsupported`) with
> specific error or availability state. The shared presentation is delayed to
> avoid flashes, visible outside the rails, and retained in
> Cockpit. One continuous overlapping load interval retains the strongest
> terminal outcome (`failed`, then `cancelled`, then `complete`) until every
> participant settles, so a later success cannot mask an earlier failure.
> A participating producer's terminal error, unavailable status, or
> key-required state also outranks generic completion without requiring a
> terminal outcome (`failed`, then `key required`, then `cancelled`, then
> `complete`) until every participant settles, so a later success cannot
> mask an earlier failure. A participating producer's terminal error or
> unavailable status also outranks generic completion without requiring a
> separate manager failure event; AIS first-connect expiry therefore ends as
> `LOAD FAILED`, not `LOAD COMPLETE`.
> `LOAD FAILED`, not `LOAD COMPLETE`. A producer whose only problem is a
> missing provider key (`stats.keyRequired`) ends the batch `KEY REQUIRED`.
> Slow disable work is labeled as turning live data off rather than
> as a completed load. Street Traffic's dedicated sync chip shows genuine
> work and one bounded completion; steady TomTom coverage, including 0%, does
+1 -1
View File
@@ -34,7 +34,7 @@ hardware-rendered overlay scenes.
These frame rates were measured when the globe was capped at 60 FPS. It now
draws at the display's refresh rate while anything moves and ticks at most 60
times a second when parked (the Cesium frame port's idle rate,
times a second when parked (the render governor's idle rate,
`IDLE_FRAME_RATE` in `src/renderGovernor.js`).
The initial-settle measurement is the more useful launch reference because it