Manuel Astudillo
Manuel Astudillo
This will difficult to fix if indeed is an issue because it does not seem related to BullMQ per se but to IORedis, and because we do not have a...
@grahamb I wish it was so easy as to just add support to ESM, the problem is that it breaks other stuff... I wrote this piece of post maybe it...
> I guess I need to search for a replacement jobs processor if BullMQ isn't going to be compatible with modern node Or you can provide a working solution too.
This is due the way Node works. Depending on the context where you put Bull (i.e. the settings in the package.json of the application depending on Bull) it may break...
> I am trying to understand what blockers exist in this library or node itself order to support this feature? Me too. It is super difficult to get it right,...
I am not sure this is correct. You must store offset because the offset is calculated in the first iteration and then you must use that offset from that time,...
But if you do not save the offset, how can you know which delay to apply to the next iteration job?
Unfortunately adding jobs does require using .lua scripts as the adding operation is too complex to be implemented using a standard Redis multi. Technically it should be possible to just...
I think standard Redis Pubsub basically does this already, does it not work for your use case?
Closing as no actions to do here.