Not switched on
Useful1 Signal3
The cloud event stream could redial forever, but nothing turns that on so it still gives up.
Endless reconnection is implemented but no caller enables it; the 5-attempt budget still applies.
What's wrong with this entry?
Anonymous. No account, no email.
What
The cloud session's event-stream client can be told to keep redialling forever instead of giving up after 5 reconnect attempts. Nothing in this build turns it on, so behaviour is unchanged: the budget runs out and the stream closes.
Details
- When on, exhausting the budget keeps retrying at the maximum backoff delay indefinitely, logs the attempt count as
∞, stops firing the reconnecting callback, and sends a one-shot telemetry event the first time it passes the budget. - The mode reads from two places: a
keepStreamRediallingconfig key, which nothing in the build ever writes, and an instance flag set only by a method that has no caller anywhere in the bundle. - The intent is a machine that is serving device hooks or remote tool calls for a cloud session and must stay dialled in.
Evidence
remote_connect_redialling_past_budget
Strings lifted out of the shipped bundle, so the claim above can be checked against them.