Resque::Helpers will be gone with no replacement in Resque 2.0.0.

[kforsman]

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?

[kaluznyo]

+1

[sahin]

+1

[gthiruva]

+1

[hlascelles]

+1

[apsoto]

+1

[matteomelani]

+1

[teeparham]

I began to fix this at https://github.com/teeparham/resque-loner & ended up re-writing it as a separate gem called resque_solo. The plugin's job name is still Resque::Plugins::UniqueJob so all you need to do to swap back & forth is change the gem. It removes the Resque::Helpers warnings for resque 1.25.

https://github.com/neighborland/resque_solo

[apsoto]

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.

[teeparham]

@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.

[pangkalizer]

+1

[rwojsznis]

@teeparham - neat, thanks 👍 for effort, will give it a try

[faheemmughal]

+1

[klippx]

+1

[tkalimov]

@teeparham I love the addition of the lock_after_execution_period -- exactly what I was looking for. Thank you!

[nickmalcolm]

+1

[idlecool]

+1