-
Initially reported [here](https://github.com/snitch-org/snitch/issues/80#issuecomment-2126174211).
We currently rely on thread-local state to link the checks to the currently-running test. This sta…
-
There is a new API in Node that allows for worker threads (these are different from Web Workers): https://nodejs.org/api/worker_threads.html
It looks like we can use these to exploit parallelism in…
-
In general, there should be no exceptions on worker threads, and they should only happen on the main thread. To validate this at runtime (and during test runs which should catch most instances), I pro…
htuch updated
2 weeks ago
-
Hello,
I want to ask if you are evaluating using [Node.js Worker Threads API](https://nodejs.org/api/worker_threads.html).
Could be awesome just in the future just upgrade the library and unleas…
-
Hi
I've been dealing with this issue since we moved our application from flask development application server to wsgi and I'm unable to find a solution to it
### Runtime environment
```
pyth…
-
Until recently, I assumed that when `queue_requests` is enabled, the reactor thread is completely responsibly for buffering requests, and only hands them over to the thread-pool once the entire reques…
-
Cloned latest version, installed per directions.
Blender 4.1.1 installed, latest flamenco via separate docker containers for the manager and the worker. These work fine (other than ignoring the com…
-
Figured this a bit different to the issue discussed in https://github.com/log4js-node/log4js-node/issues/822
-
```
The attached file creates 4 workers. All of them are busy looping and 2 of
them never post any messages back to the worker thread.
There is also a "perf meter" on the page measuring "laggyness" o…
-
**Describe the bug**
In the Chrome debugger I can see the worker threads from ffmpeg when the ffmpeg command has finished. I expected them to exit (but I really have no idea).
**To Reproduce**
St…