Background sessions whose terminal process died are now killed and marked failed instead of hanging.
What's wrong with this entry?
A background session whose terminal host process has exited but was never reaped is now detected, force-killed and marked failed, instead of leaving the session apparently alive.
- Reports a new telemetry event,
tengu_bg_ptyhost_zombie, carrying the session short id, how it was reached, its state, its uptime in milliseconds and how many clients were attached.
tengu_bg_ptyhost_zombie
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