Steve Jackson comments

Repositories
Issues
Comments

Results 2 comments of


                                            Steve Jackson

Problem working with resque-retry

I'm seeing this as well, it appears that the resque-status uuid that resque-retry passes back via resque-scheduler causes the enqueue_to call to fail (splatting the args causes an ArgumentError).

Problem working with resque-retry

Here's my hack, I don't think it's a good enough solution to submit a pull request ``` ruby #override because resque-retry passes in resque-status uuid as the first arg def...