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
Hi,
First i wanted to say THANKS for a great ,simple to use component.
We are using it a lot and its seems like working fine for few good months UNTIL 2 days ago.
We noticed a strange behavior lately from a very simple code:
CODE
var workerPool = require('worker-threads-pool');
var pool = new workerPool ({max: 5});
pool.acquire(destdir, {
.....
The strange part is the the pool never able to acquire a new resource and our code not callback.
Any chance that you will consider adding :
Timeout for acquiring ? so if after a specific time the pool is not acquiring it will throw an error ?
We've upgraded to v2 and we saw that there is a new maxWaiting but we are afraid that we will end up with the same problem as happened prior v2.
If needed, you can add my as a collaborator and ill help.
The reported issue is not happening all the time and we are not able to reproduce it.
Thanks!
The text was updated successfully, but these errors were encountered:
Hi,
First i wanted to say THANKS for a great ,simple to use component.
We are using it a lot and its seems like working fine for few good months UNTIL 2 days ago.
We noticed a strange behavior lately from a very simple code:
CODE
var workerPool = require('worker-threads-pool');
var pool = new workerPool ({max: 5});
pool.acquire(destdir, {
.....
The strange part is the the pool never able to acquire a new resource and our code not callback.
Any chance that you will consider adding :
Timeout for acquiring ? so if after a specific time the pool is not acquiring it will throw an error ?
We've upgraded to v2 and we saw that there is a new maxWaiting but we are afraid that we will end up with the same problem as happened prior v2.
If needed, you can add my as a collaborator and ill help.
The reported issue is not happening all the time and we are not able to reproduce it.
Thanks!
The text was updated successfully, but these errors were encountered: