The device bridge now stops itself mid-session if its switch flips off, but it's off by default.
A default-off device bridge now watches its own gate and shuts down, reporting whether the flag or the egress gate stopped it.
tengu_violin_wood Off in both readingsThe flag server returned off for the account this site reads and for the anonymous baseline. A reading of off cannot rule out a rollout these two readings sit outside of.
This account: off · anonymous baseline: off · compiled default in v2.1.235: on
Read once, for one account on one subscription tier, against v2.1.235. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
The device bridge, which is gated behind the flag tengu_violin_wood (default off), now watches for that flag flipping off during a session and shuts itself down. Stop reasons are distinguished: gate_off when the feature flag turns off, egress_denied when the network-egress gate refuses.
- The default liveness check treats a flag value served from the payload, an override, or an explicit disable as "now off"; a mere absence of any served value does not stop it.
- Two injection points,
isStillEnabledandonEnabledChange, are read at the default site but nothing in this build supplies them, so they are seams for tests or an embedding host rather than a live path. - The bridge also now reports whether it has unsent changes, how many calls are in flight, and an idle signal to the session.
[deviceBridge] stopping: the gate turned off
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.225
Device bridge lifecycle telemetry
Both mention device bridge
-
v2.1.229
Device tools moved into a de-duplicating registry
Both mention device bridge
-
v2.1.229
Device binding reports attestation and counts dropped events generically
Both mention device bridge