Stalled watches now wait 2-4 minutes between retries and give up at a random point between 30 and 45 minutes.
tengu_slate_lantern_ember On for this account, and not off by defaultThe flag server returned on for the one account this site reads, and nothing in this release compiles it off by default. The compiled default is shown below, and says which it is when we cannot read one: a fifth of gates compile in a string or a number rather than on or off, and most published releases have no gate table behind them at all. No client can see what the server returns for your account.
This account: on · anonymous baseline: on · compiled default in v2.1.250: on
Read once, for one account on one subscription tier, against v2.1.250. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
Repeated reconnect stalls now back off 2 to 4 minutes instead of 30 to 60 seconds, and a stalling watch gives up somewhere between 30 and 45 minutes rather than at exactly 30, so clients in one outage do not all abandon at the same moment. The long band is picked when a stall repeats and either the connection was closed by Cloudflare mitigation or lease mode is off, and lease mode (tengu_slate_lantern_ember) defaults to off, so a stock build takes the long band.
- New timing constants:
longStallMinMs: 120000,longStallMaxMs: 240000,stallOutJitterMs: 900000. - Give-up deadline is now per run:
maxStallMsplus a random amount up to the jitter. - A counter event fires once per stall run carrying a startup flag and, when known,
http_status. - The numbers are compiled in and copied into state; nothing in this build overrides them remotely.
stallOutJitterMs, stall_run_started
Strings lifted out of the shipped bundle, so the claim above can be checked against them.