Anna
Anna
This is needed!
@andywer Pretty much methods like: `.clearQueue()` would clear the entire pool queue (tasks that are still waiting for a worker to be free) `.cancelTasks()` I named it **cancelTasks** because perhaps...
The thing is, some tasks can take longer than others, and the pool has 6/7 workers. And i can't really check which specific task is running on a certain worker...
> Hey @aya1337. Have you tried to enable debug logging? > > https://threads.js.org/usage-advanced#debug-logging I didn't try debug logging, no idea how that went past my head Had to seperate the...
Hello, it has happened again... I used debugging and this is what is happening (Keep in mind that the same code above is used and the same scenario as above...
@andywer I was actually typing it haha. Thanks for the update. It unfortunately did not solve the issue. Tasks keep pilling up endlessly, the workers all have runningTasks that never...
I believe you are right. I just got confused on how the same behaviour happened even when I didnt use the variable where I awaited `const asyncStuff = [...(await asyncFunction())]`....
@andywer 1. Latest version https://github.com/andywer/threads.js/commit/9fa13af4a99d11a844899f022590139d6fb101ac 2. Yes, I'm using tiny-worker fallback (sorry for failing to mention that) 3. I tried the default (4), tried 8, even tried just 1 (for...
Any update on this one?
> It's an OpenSource Project so you can make a PR if you want progress. Why would I comment here if I was able to do it myself? like can...