node-resque - npm Package Compare versions

Comparing version 0.16.4 to 0.16.5

lib/plugins/queueLock.js

		@@ -34,6 +34,3 @@ // If a job with the same name, queue, and args is already in the queue, do not enqueue it again
		self.worker.connection.redis.set(key, timeout, function(err){
		self.worker.connection.redis.get(key, function(err, redisTimeout){
		redisTimeout = parseInt(redisTimeout);
		callback(null, now > redisTimeout);
		});
		callback(err, !err);
		});
		@@ -40,0 +37,0 @@ }

package.json

		@@ -5,3 +5,3 @@ {
		"description": "an opinionated implementation of resque in node",
		"version": "0.16.4",
		"version": "0.16.5",
		"homepage": "http://github.com/taskrabbit/node-resque",
		@@ -8,0 +8,0 @@ "repository": {

README.md

		@@ -150,2 +150,3 @@ # node-resque
		- When ending your application, be sure to allow your workers time to finish what they are working on
		- This project impements the "scheduler" part of rescue-scheduler (the daemon which can promote enqueued delayed jobs into the work queues when it is time), but not the CRON scheduler proxy.
		- If you are using any plugins which effect `beforeEnqueue` or `afterEnqueue`, be sure to pass the `jobs` argument to the `new Queue` constructor
		@@ -152,0 +153,0 @@ - If a job fails, it will be added to a special `failed` queue. You can then inspect these jobs, write a plugin to manage them, move them back to the normal queues, etc. Failure behavior by default is just to enter the `failed` queue, but there are many options. Check out these examples from the ruby ecosystem for insperation:

Improved metrics