Device Information (please complete the following information):
Deployment: [Linux, Linux ARM64 or Docker] Docker
SIST2 Version: [e.g., v2.9.0] 3.4.1
Describe the bug
If a task locks up and you cannot kill it, I usually end up just restarting the Docker container.
But then there is no record of that task in the Task History and the Log files are not available.
Expected behavior
The Task is added to the Task History with a link to the newly created log file as soon as the Task is started (I guess, instead of when it is finished?)
(Is there a different way I should handle a frozen task?)
Device Information (please complete the following information):
[Linux, Linux ARM64 or Docker]Docker[e.g., v2.9.0]3.4.1Describe the bug
If a task locks up and you cannot kill it, I usually end up just restarting the Docker container. But then there is no record of that task in the Task History and the Log files are not available.
Expected behavior
The Task is added to the Task History with a link to the newly created log file as soon as the Task is started (I guess, instead of when it is finished?)
(Is there a different way I should handle a frozen task?)