v2.1.1

(bug) worker.performInline needs result and error passed to worker for plugins

v2.1.0 worker#performInline

worker#performInline

DO NOT USE THIS IN PRODUCTION. In tests or special cases, you may want to process/work a job in-line. To do so, you can use worker.performInline(jobName, arguments, callback). If you are planning on running a job via #performInline, this worker should also not be started, nor should be using event emitters to monitor this worker. This method will also not write to redis at all, including logging errors, modify resque's stats, etc.

queue.locks and queue.delLock

Adds queue.locks() and queue.delLock() to help manage your resque locks.

v2.0.8

Fixes a memory leak in queue.stats

2.0.7: queue.stats

queue.stats() will let you inspect the resque stats of your cluster (failed, processed, etc)

v2.0.6 EventEmitter Warning

Prevents (node) warning: possible EventEmitter memory leak detected. 2 error listeners added. Use emitter.setMaxListeners() to increase limit warning when using multiWorker.

We now increase the number of listeners on the redis connection rather than set it explicitly.

Worker internals to expose result

This release should have no visible changes to how node-resque works. We now expose worker.result so it can be manipulated via plugins.

by @gcoonrod via #136

v2.0.4: Bugfix

Fix delayed job removal

• Prepend queue namespace to delayed job key found in timestamps before attempting to remove from delayed queue list, and added check that the removal was successful.
• Created new test, and fixed another which was returning done() multiple times because of the changes to delDelayed.

By @ccapo via #133

v2.0.3: Bugfix

Fix a bug which would prevent the showing of errors from an early plugin when running more than one plugin.

• by @evantahler via 17bc8d4

v2.0.2

Bugfix for resque-retry. If a job which did not fail used the plugin, it would be noted as failed :(