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
Allow sidekiq_delay and not just delay #5
Conversation
I'd be happy to accept a PR which checks for |
Please could you add a test, then I can merge. Thanks. |
Ok great, will do once I get off work. It should probably belong in a separate |
No problem :) |
@krisleech : I get
should i submit a separate PR? |
A PR would be great. It needs to be backwards compatible, so check for I think the order should be |
ok, i'll give it a try. I'm pretty new to this :) On 18.11.2015 at 09:06 GMT None wrote:
|
@krisleech it seems that the problem is bigger: just replacing Any thoughts on what could be the best solution in this case? |
@movstox I'm happy to help. It doesn't sound like One thing I will ask - does your listener |
@krisleech take a look at this movstox@a0b34a5 It fixes spec tests, but I doubt it's backward compatible. |
The code looks fine but I think it fixes a problem you don't have, see previous comment :) |
That is unless you want your listener to also be a Sidekiq worker as you'll also use it outside of Wisper... |
@krisleech https://github.com/mperham/sidekiq/blob/master/lib/sidekiq/worker.rb#L42 raises an exception if I run spec on your current |
Did you you remove the |
The Sidekiq master branch still has I think the error you are getting is because Wisper is calling |
@krisleech I see now, sorry for confusion and thanks for your help! |
No problem :) Did it solve you problem, if so, can you close the issue please. |
(sorry I see it isn't your issue) |
Hello,
Great gem, love it. Today I was having trouble with async calls to the subscriber and I noticed that the jobs are sent to sidekiq via
delay
. This is problematic if you use delayed_jobs and sidekiq in the same project. A workaround to this is to usesidekiq_delay
, which you can turn on viaSidekiq.hook_rails!
https://github.com/mperham/sidekiq/wiki/Delayed-extensions#disabling-extensions
I'm not sure if there is a better way to do this (maybe there is an internal setting in Sidekiq that can be checked), but just wanted to present one way to fix it.
If you wanted to accept this version, I can also write a quick test for it.