Jeremy

+1 .uniq kills the query

Switching version is high risk, our business depends on our ability to process million of jobs properly. We may keep that in the bag as a last resort, right before...

Ok, that's noted and useful information. Looking at the change log, there are some very scary bugs I would not have loved to run into. I wonder if spotify ran...

Good to know they are involved. I don't need a big documentation, can you summary in 1-2 lines the fundamental change of approach in implementation between 6 & 7?

We moved to version 7 too. I think it would be easier to simply say you don't support version 6 because that's kind of the case already since all answers...

Still the case in end of 2015 unfortunately.

Thanks for the reply & confirming this is not possible @yivo

+1 this tool is instrumental for my productivity on Mac :/

Using Heroku & resque-pool, how do I signal USR2 so jobs complete but no new resque jobs are executed? I'm happy (and prefer) to not process enqueued jobs with old...

This is the work around I did: I added a Resque "before_enqueue" hook. Inside, I check for a flag in redis to know if I paused the processing or not....