Under the hood
Useful1 Signal2
Background workers are now told why they are being stopped, such as a config reload.
What's wrong with this entry?
Anonymous. No account, no email.
What
Stopping a daemon worker sends a reason along with the shutdown, so a worker can tell an upgrade apart from a config reload. On reload the supervisor passes "reload" when the worker's session still exists in the new config.
Details
- Restart now stops every worker first and then starts them back in a staggered sequence, rather than stopping and starting each one in turn.
Evidence
{ type: "shutdown", cause: t }
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.234
Background task notifications arrive inside a system-reminder
Both mention background task
-
v2.1.235
Several finished background tasks now report as one line
Both mention background task
-
v2.1.236
Background-task notices no longer look like user approval
Both mention background task