Thanks for the bug report, but I dont I understand what the problem is you are seeing.
Is your situation like this:
1-Job is submitted to worker
2-Worker starts execution of job
3-Worker is stopped while Job is still running
If that is the case, then the correct behavior would be what you are seeing. We should only send a job_completed packet if the job has finished. Stopping the worker does not mean the jobs itself has finished.
Or is the situation you are seing like the following:
1-Job is submitted to worker
2-Worker starts execution of job
3-Job completes
4-Worker is stopped
Hi Darren:
Thanks for the bug report, but I dont I understand what the problem is you are seeing.
Is your situation like this:
1-Job is submitted to worker
2-Worker starts execution of job
3-Worker is stopped while Job is still running
If that is the case, then the correct behavior would be what you are seeing. We should only send a job_completed packet if the job has finished. Stopping the worker does not mean the jobs itself has finished.
Or is the situation you are seing like the following:
1-Job is submitted to worker
2-Worker starts execution of job
3-Job completes
4-Worker is stopped