Jobs still run after context is done

[BredSt]

HI,

I've some time to run some extended test (on the master branch code ) and I found one issue.:)

in case you provide a timeout and retry to specific task you are getting the error that the time passed which is ok. However, the task is proceed and continue to run which is problematic as the timeout should win.
User should define a timeout as limit to the task and after the job exceed the timeout it should be killed to free resources as if it pass the results after the timeout the results is not valid anymore...
as the jobResults := wp.StopWaitXT() should handle it.
WDYT?

[oze4]

Do you have some code I can test with?

Let's say you have a job that sleeps for 1 hour but your timeout is 1 second. How would you go about cancelling a job that is just sleeping (or in flight)?

[oze4]

This one is really stumping me.... I reached out to the author of workerpool (gammazero/workerpool#40) for help on this.. I think it is out of my understanding of Go as to why this is happening.

You can view a better POC here

Any idea how to resolve this?

[BredSt]

HI,

I saw that you got a nice answer which solve the problem :-) , when to expect to new version as we want to run it on prod.

Thanks!

[oze4]

@BredSt what makes you think the problem is resovled?

[BredSt]

Hi @oze4 - this replay #7 (comment), but I understand that it a bit tricky :( as the tread continue..., now I saw this gammazero/workerpool#40 (comment)
Do you think that we have a solution to this problem?

[oze4]

Closing per