-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Resque::Helpers will be gone with no replacement in Resque 2.0.0. #32
Comments
+1 |
5 similar comments
+1 |
+1 |
+1 |
+1 |
+1 |
I began to fix this at https://github.com/teeparham/resque-loner & ended up re-writing it as a separate gem called |
When you say rewrite does that mean it's not a simple fork plus patch? Loner has been stable for so long 'rewrite' concerns me. |
@apsoto Re: resque_solo: The tests are basically the same. I used fakeredis instead of an actual redis server in test. I re-structured the internal classes. I started with a blank project & copied many of the tests and much of the code. We're running it in production, if that helps. |
+1 |
@teeparham - neat, thanks 👍 for effort, will give it a try |
+1 |
1 similar comment
+1 |
@teeparham I love the addition of the lock_after_execution_period -- exactly what I was looking for. Thank you! |
+1 |
1 similar comment
+1 |
Hi there, thanks for a great gem. I have started to see this warning in the logs (Resque::Helpers will be gone with no replacement in Resque 2.0.0.), looks like it stems from resque-loner. Any plans to make it compatible with Resque 2.0?
The text was updated successfully, but these errors were encountered: