Manuel Astudillo

Results 932 comments of Manuel Astudillo

it is as if it is retrying the command also, but if the command timed-out we should not retry it as it just thrown an exception.

@godinja in your case, couldn't you just serialize the decimal.js types before adding the job data? In other words, it should be easy enough to build a custom serializer on...

@fifa334 could you please give us a code snippet that reproduces your issue?

@fifa334 I think you have some misconceptions on how workers and concurrency work in BullMQ, so your questions are not really making a lot of sense :) To summarise. 1...

yes, I am sorry but I am a bit reluctant to increase the complexity so much for a quite small feature addition... complexity keeps adding up and then it is...

Can you produce the complete source code, as the one that you provided is not enough as it is not adding any jobs and so on.

Btw, jobs are not "drained", the drained event is generated when the queue is empty, i.e. there are no jobs to be processed.

Furthermore, by definition this code is going to generate a leak: ```ts { connection: new IORedis({ host: env.REDIS_HOST || 'localhost', port: Number(env.REDIS_PORT) || 6379, maxRetriesPerRequest: null, }), ``` As you...

I am running this code which creates something like 1k jobs per second, and I keep it running for some time, like 10 minutes or so, running the garbage collector...

Here some proof that there are no leaks, after 15 minutes running I took a new heapshop and all the allocations produced between 1 and 2 (processed thousands of jobs...