chain-studio/lib/l10n
flemming-it ea2cd87b5e fix(runs): stop claiming the hub is unreachable on RPC-level errors
The runs monitor folded every load failure into 'hub not reachable',
contradicting the sidebar's green connected dot whenever the hub
answered but the RPC failed — most visibly against a pre-0.22 hub
whose version predates the ListInvocations RPC (UNIMPLEMENTED).

Classify the failure instead (top-level, unit-tested):
- UNIMPLEMENTED -> 'this view needs a newer hub version' with a
  doctor-page link (the update banner lives there)
- FAILED_PRECONDITION from the detached gate -> the regular
  feature-off empty state with the guide button
- UNAVAILABLE / DEADLINE_EXCEEDED / socket-level failures -> the
  honest 'hub not reachable' state (unchanged)
- everything else -> a load-failed state with the friendly error
  and a copyable detail box

The error view is a public callback-driven widget so the tests pump
each variant without a live hub. New DE+EN strings for the too-old
and load-failed states; grpcCodeOf/grpcMessageOf exposed from the
friendly-error mapper instead of duplicating the duck-typing.

Signed-off-by: flemming-it <stefan.a.flemming@googlemail.com>
2026-07-18 17:33:11 +02:00
..
app_de.arb fix(runs): stop claiming the hub is unreachable on RPC-level errors 2026-07-18 17:33:11 +02:00
app_en.arb fix(runs): stop claiming the hub is unreachable on RPC-level errors 2026-07-18 17:33:11 +02:00
app_localizations.dart fix(runs): stop claiming the hub is unreachable on RPC-level errors 2026-07-18 17:33:11 +02:00
app_localizations_de.dart fix(runs): stop claiming the hub is unreachable on RPC-level errors 2026-07-18 17:33:11 +02:00
app_localizations_en.dart fix(runs): stop claiming the hub is unreachable on RPC-level errors 2026-07-18 17:33:11 +02:00