Completion notices would carry a finished task's output tail, on a disabled path.
Part of the background-task delivery path compiled off in this build.
What's wrong with this entry?
On the delivery path that is compiled off in this build, a finished background task's output tail is read before the completion notice goes out, so the notice would arrive with the tail attached.
- If the read fails, the task is delivered without the tail and a warning "output tail unreadable, delivering without it" is logged.
- Sits behind the same compiled-off guard as the GetTask surface, so nothing reaches users here.
output tail unreadable, delivering without it
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