You'll notice
Useful3 Signal3
After reconnecting, replayed old output no longer makes a dead cloud worker look alive.
What's wrong with this entry?
Anonymous. No account, no email.
What
After reconnecting and resuming from a saved position, the CLI could treat old frames being replayed as evidence that the remote worker was still running. Frames are now compared against the time the current connection opened and marked as replayed if they predate it, and only fresh worker frames count as proof of life.
Details
- The comparison allows 2 seconds of slack; a frame whose date cannot be parsed is conservatively treated as replayed.
- The connection time comes from the response
dateheader when the server sends one. - Frames also carry a worker epoch integer read off the frame.
- Applies to all cloud sessions on this build, with no setting to turn it off.
Evidence
t.source === "worker" && t.replayed !== !0, connectedSince
Strings lifted out of the shipped bundle, so the claim above can be checked against them.