The background worker stops killing its own processes

On a board short of memory, Anthias kept stopping and restarting parts of itself, which cost the board time and memory it didn't have. It was the largest single problem in the crash reports Anthias devices send the project. Anthias 2026.10.0 stops it, and upgrading is all you need to do.

Anthias runs uploads, downloads, video probing and housekeeping in a background worker, the anthias-celery container. That worker kept killing its own idle processes and starting replacements. Its log filled with lines like these:

Process 'ForkPoolWorker-3' pid:412 exited with 'exitcode 1'
Timed out waiting for UP message from <ForkProcess(ForkPoolWorker-4, started daemon)>

The trigger was the soft time limit, the warning a task gets before its hard limit cuts it off. On a busy board that warning could arrive after the task had already finished, and the idle process that received it exited. From Anthias 2026.10.0, a warning that arrives when no task is running, or that was meant for an earlier task, is ignored. A task that really runs past its soft limit is still stopped, and one that hangs is still cut off by its hard limit.

The tasks that read the display's power state over HDMI-CEC and send telemetry could also catch the warning meant for them, carry on, and get killed by the hard limit. They now stop when they're told to.