Remote-control upgrades now wait for a worker to go idle instead of cutting sessions off.
tengu_daemon_upgrade_defer_busy Not enough to sayNothing here resolved what this flag was doing on this version, so nothing here should be read as on or off.
This account: no value returned · anonymous baseline: no value returned · compiled default in v2.1.248: off
Read once, for one account on one subscription tier, against v2.1.248. It isn't a statement about your account. What a flag value here can and cannot tell you
What's wrong with this entry?
A worker process that handles remote-control sessions now tells its parent daemon whether it has active sessions, sending busy and idle transitions plus a repeating keepalive while work is in flight. The daemon uses this to defer restarting for an upgrade until the worker goes idle, rather than interrupting live sessions.
- Deferral is gated on
tengu_daemon_upgrade_defer_busy, which falls back to on when the server returns nothing. - The worker sends a message of type
rc_busycarrying the current busy flag. - The same busy flag decides whether active sessions are persisted when the worker shuts down.
- The worker does not decide to stop on its own: it waits for the parent to push a shutdown message whose cause is
upgrade,reloadoryield, and exposes that cause so the upgrade path can act on it.
rc_busy, process.send({ type: "rc_busy", busy: g })
Strings lifted out of the shipped bundle, so the claim above can be checked against them.