You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This seems pretty important. Looking into using compute-cluster for kumascript, and child processes have been known to die in production for initially mysterious reasons (ie. eventually discovered bugs, resource limits, etc).
The workaround I'm looking at right now is to start a timeout before enqueue, and to just bail out if the enqueue callback never gets called before the timeout fires. Workable, but is a bit awkward.
shall the client be able to cancel enqueued work? or specify a timeout - the max time it should take?
The text was updated successfully, but these errors were encountered: