Under the hood
Useful2 Signal2
Background tasks that die are now distinguished from ones that finish normally.
What's wrong with this entry?
Anonymous. No account, no email.
What
The step that decides a background task has come to rest now reports three outcomes instead of two: a dead worker generation, a normal settle, or nothing to do.
Details
- Dead generations record a
deadEpochReapedAttimestamp rather than the mid-work reap timestamp. - In that case the first terminal time is taken from the previous update time instead of the current one.
Evidence
deadEpochReapedAt
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