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
The behavior of kue.createQueue({ worker: false }) is inconsistent with the documentation.
Currently, this flag only controls whether or not the queue will process jobs created with .every(). Queues created as "non-workers" will still process jobs in all other circumstances.
In the following example, the job gets processed, even though the queue has been marked as a "non-worker".
varQueue=kue.createQueue({worker: false});varjob=Queue.createJob('myJob',data).attempts(3).backoff(backoff).priority('normal');Queue.schedule('3 seconds from now',job);Queue.process('myJob',function(job,finalize){console.log('Hello World!');finalize();});
The text was updated successfully, but these errors were encountered:
What do you think the appropriate behavior should be? Should Queue.process() throw an error if we try to call it on a non-worker, or should it simply not do anything?
My current setup contains micro services which I don't include the processing code for non workers. There's no good reason to have non-workers include that extra code anyway.
The behavior of
kue.createQueue({ worker: false })
is inconsistent with the documentation.Currently, this flag only controls whether or not the queue will process jobs created with
.every()
. Queues created as "non-workers" will still process jobs in all other circumstances.In the following example, the job gets processed, even though the queue has been marked as a "non-worker".
The text was updated successfully, but these errors were encountered: