Bean

> EDIT: and then it makes sense to me to offer this as the only way to add an abort listener, for both offloaded and dedicated workers, right? Yes this...

@josdejong Question on how errors are processed. Since `cancel` and `timeout` produce unique error types. and upon an error received over the worker rpc bridge will cause `terminate` to be...

> Thanks for the updates! I added a few inline comments. > > About the WorkerHandler terminating the worker when receiving a `cancel` or `timeout` error: that is a very...

> Ow nice I didn't know that you can draw a sequenceDiagram straight in GitHub issues 😎. > > I'm not sure whether a queue is really needed since a...

Hey @josdejong I think I have made good progress and was able to implement the feature set we have discussed above where 1) We are able to prevent the termination...

@josdejong Made the updates. Going to start on Docs/example. Update: Example and docs updates are ready.

@josdejong After running the test suite with `--detect-leaks` I have found the test which is causing the `Pool` test suite timeout `should clear all workers upon explicit termination` Will look...

> 2\. assert.strictEqual(stats.totalWorkers, 1 > Thanks for the updates. The PR is almost ready now! Remaining things: > > 1. Fix the `recieve` typo > 2. Can you please a...

> Sounds good, thanks! > > I've done some debugging. The timeout error occurs in `Pool.test.js`. I've removed all as much tests as possible to create a minimal version of...

So With commit c68cc9b I have been able to get `Pool should timeout a task` to complete tear down, along with all other tests within `pool`. So it looks like...