Force Pause

[pyrostew]

Is your feature request related to a problem? Please describe.
Node schedules don't pause the running job, only stops a node from picking up a new job.

Describe the solution you'd like
In the same vein as the Soft Pause option that was added a little while back, maybe a "Force Pause" option on the schedules would be good as well. Though I get the impression from reading through past issues that "Pause All Nodes" should pause the current jobs on all nodes when the "Soft Pause" option is disabled?

Describe alternatives you've considered
I've tried various combinations and permutations of schedules, pausing nodes, changing the number of workers on a node etc., but the behaviour always seems to be "soft pause" even though I have that option turned off, and I have compared with having the Soft Pause option on as well, same behaviour.

Additional context
I've just started using Tdarr because of the scheduling feature, with the intention of making best use of the power of an old server when no one is in the house, and then having jobs pause on schedules to keep the server quieter when people are home. Problem is the schedules aren't particularly useful when there isn't an option to pause the running job. Some of these jobs take 6 or 7 hours so simply saying the node will finish the current job and then pause doesn't work when the server could be running at full tilt for another 5 or 6 hours.

[HaveAGitGat]

Was covered here and a few other issues.
#199 (comment)

Also these days Tdarr is used for far more than just transcoding and so pausing all sorts of different processes mid-process in a crossplatform manner isn't possible unless you get into OS process suspension which can have it's own issues.

Open to suggestions though but not a focus atm.

[pyrostew]

I would agree that most of the various tasks probably don't need an option to pause during the task as most of them probably only take a few minutes at most so simply pausing at the end of the task isn't really an issue. but for common tasks that could run for hours, particularly handbrake and ffmpeg transcodes, waiting till the end of the task to pause is quite significant.

This feels like something that could be done on the big common tasks without too much effort, and the rest don't run for long enough for it to be an issue.

[pyrostew]

I would have a look myself, but I'm struggling to navigate the structure of the codebase at first glance.

[HaveAGitGat]

Here's where we spawn the process in flow:

https://github.com/HaveAGitGat/Tdarr_Plugins/blob/2f1ca65f1705d4fe3c36b71ab6ab3164d12397af/FlowPluginsTs/FlowHelpers/1.0.0/cliUtils.ts#L374

We could use this.config.updateWorker to add the PID to the worker, and the have a pause/unpause event on the node