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

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

Open kforsman opened this issue 10 years ago • 16 comments

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?

Sep 23 '13 05:09 kforsman

Oct 07 '13 10:10 kaluznyo

Oct 11 '13 21:10 sahin

Nov 07 '13 22:11 gthiruva

Nov 14 '13 16:11 hlascelles

Nov 25 '13 17:11 apsoto

Nov 27 '13 16:11 matteomelani

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

Dec 17 '13 06:12 teeparham

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.

Dec 18 '13 05:12 apsoto

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

Dec 18 '13 05:12 teeparham