Unexpected results when using runImmediately with job.stop()

[thenorthernpole]

Hi,

I see a logical issue with combining runImmediately with job.stop().
If a job is set to runImmediately, invoking job.stop in its first run will only affect the second run.
So the job will be executed twice, instead of once.

const doMyThing = async (cancellationCallback) => {
     // do something
    cancellationCallback(job)
}

const jobCancellationCallback = (jobToCancel) => {
    jobToCancel.stop()
}

const task = new AsyncTask('Some Fun', () => doMyThing(jobCancellationCallback))
const job = new SimpleIntervalJob(
    { seconds: 2, runImmediately: true},
    task,
    {
        id: 'id_1',
        preventOverrun: true,
    })

Thanks!

[raliqala]

If a job is set to runImmediately, invoking job.stop in its first run will only affect the second run.
Hi
Your statement is correct, the job will run the task once then stop it won't run twice because after stop it stopped.

[thenorthernpole]

Hi, thanks for the reply.
My intention was that it will run twice before stopping.
E.g. the first run will execute the stop but the stop won't work and will thus invoke a second run.
The stop will only prevent the third run.
It only happens with runImmedaitely (as if it invokes an additional task, instead of using the same one)

[kibertoad]

Thank you for reporting. I'll look into this.