UI5 / cli / 30099947871

94%

push

github

refactor: Split server activity state from stale-project tracking (#1474)

The server banner mixed two separate things into one `#serverState`
value: what the server is doing (activity) and which projects are
up-to-date (staleness). Any non-fresh project forced the whole server to
`stale`, including a dependency that is merely `INITIAL`, never
requested, with a stale cache. Under lazy building nobody rebuilds an
unrequested project, so the server got stuck on `stale` and never
returned to `ready`, even though every resource was still servable on
request.

- **Activity (`BuildServer`'s `#serverState`)** drops `STALE`. The
resting state is `IDLE`, rendered as `ready`. `#reconcileServerState`
settles on `IDLE` whether projects are fully fresh or stale-remaining;
background validation still runs first when `INITIAL` projects may be
cache-clean.
- **Stale set** is reported independently via a new `#emitStale()`,
de-duplicated against the last set so the several emission sites
(reconcile, eager source-change, watcher recovery, startup) don't
re-emit an unchanged signal.
- **Logger side**: `Serve#stale(staleProjects)` replaces
`stale(changedProjects)`. `InteractiveConsole` records the set on
`serve-stale` and re-renders without an activity transition; the `ready`
line appends a dimmed `· N projects stale` count. The standalone `stale`
render state is removed.

6952 of 7648 branches covered (90.9%)

Branch coverage included in aggregate %.

13187 of 13732 relevant lines covered (96.03%)

5440.89 hits per line