-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
90%: working multiple queues #1
Conversation
#API agnostic for Resque 2 with duck typing on requeue_and_remove | ||
def reque_single_job(id) | ||
def requeue_single_job(id, queue) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 for correcting spelling
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
DEATH TO AMERICAN SPELLING!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do you think que
is American?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I stand corrected - Spanish then!
90%: working multiple queues
Gets resque-web to work with multiple failure queues when using the 1.25.2 API with a fix around multiple failure queue backends (resque/resque#1234)
This isn't tested with the resque 2.0 API, especially around the retrying of all jobs due to requeue_and_remove not accepting a queue name parameter.
Currently the Gemfile specifies the talis fork of resque, however, once the multiple failure queue backend fix has been merged in, this should be good to use with mainline resque.