Manuel Astudillo
Manuel Astudillo
@digipigeon any chance you could provide a snippet that reproduces this issue? that will be very helpful so that we can also provide a solution that addresses specifically your problem.
```job.log``` is an asynchronous call, so you must await it: ```await job.log('Starting Alert');```
> > Hello, > > I have just noticed the change to 5.53.1 for the closure of [#3269](https://github.com/taskforcesh/bullmq/pull/3269). I have just updated and ran a test and I am sorry...
> Hi [@manast](https://github.com/manast) sorry I just wanted to confirm something... > > Most of the time I am building applications for performance and waiting for logging to write is not...
closing as we do not have any reproducible test code nor any feedback to our latest replies.
Thanks for reporting this issue.
One thing that I forgot to mention, the interface should be properly documented using typedoc syntax, similarly as we document the rest of the API: https://typedoc.org/example/
As far as I know BullMQ is as stable as Bull having a much larger test suite, so in general you should not have more issues, but less. However it...
9 out of 10 the errors of this nature steams in wrong passing of options or arguments when not using Typescript, specially coming from Bull which does not have the...
> I am having the ssame issue. It happens randomly and I cannot even destroy the queue. I have to restart each time. It is highly unlikely that you are...