Terminal cleanup targets the right process instead of killing the whole group.
What's wrong with this entry?
When the background daemon tears down a terminal worker, it now checks the recorded REPL process before falling back to killing the whole process group, on top of the existing attempts to close sockets. This makes cleanup less likely to kill more than it should.
- The check uses the process id and start time stored for the worker, so a recycled process id is not mistaken for the original.
- Unconditional part of background worker cleanup.
await UV(A.replPid, A.replProcStart)
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