Jason 415e8994ef fix(failover): refresh the routing marker after the proxy fails over ...

When the proxy fails over (a circuit breaker trips, or a reordered queue
sends requests to the new head), the backend only updates the device
route pointer via record_failover_route and emits provider-switched. The
App listener answered that by refetching the ["providers", app] list
query alone, but the panel's "routing" marker reads routeProviderId from
the separate, unpolled ["providers", app, "mode"] query, so it stayed on
the old provider until something else invalidated the prefix.

Invalidate the whole ["providers", appType] prefix on provider-switched
instead, for any app, and add an App integration test that fails without
the fix.

Refs #7998

2026-10-17 18:25:07 +08:00

..

App.test.tsx

fix(failover): refresh the routing marker after the proxy fails over

2026-10-17 18:25:07 +08:00

SettingsDialog.test.tsx

fix(settings): use confirmed directories for unrelated autosaves (#8023)

2026-10-12 17:43:05 +08:00