Background daemon start failures now name a cause, and a sleeping machine gets one retry.
What's wrong with this entry?
When the background daemon fails to start, the failure now carries a cause: wrapper, ask, spawn, timeout, exited, or the operating system's spawn error code. A child that died is reported separately from one that simply never answered. If the wall clock jumped during a cold start, typically because the machine slept, and the daemon is still unreachable, the whole start is retried once.
- Telemetry gains
child_exited,exit_code,exit_signal,budget_extendedandclock_jump_retry.
retrying the whole start once
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.248
Background daemon can retire a same-version instance
Both mention background daemon
-
v2.1.248
The background daemon defers restarts and idle exits while an upgrade is pending
Both mention background daemon
-
v2.1.248
Stale background worker rosters no longer trigger upgrade respawns
Both mention background daemon