Weird issue with Sidekiq calling wrong method.

[Angel Jose]

I have two sidekiq workers sending out sms's through Twilio.

class SmsWorker

  include Sidekiq::Worker

  sidekiq_options :rate => {                #sidekiq rate-limiter gem

    :limit => 1,

    :period => 180,

  }

  def perform(user_id)

    Sidekiq.redis do |conn|

    user = User.find(user_id)

   if user.invitation_sms

       user.update_attributes(:invited => true, :sms_invite_date => Date.today)

   end

 end

  end

end

class HatsWorker

  include Sidekiq::Worker

  def perform(user_id)

    Sidekiq.redis do |conn|

    user = User.find(user_id)

      user.know_sms

 end

  end

end

from rails console, I can call user.know_sms and send the correct message. But if I try HatsWorker.perform_async(user.id) then a totally different method is executed (user.need_sms).

I have deleted this worker, renamed it, replaced which folder it's loaded from, etc. etc. etc. Can't seem to crack it. Any help would be appreciated!

[Mike Perham]

Sounds like you have Spring running and caching your code.

Why do you have `Sidekiq.redis` around all your worker code?

--
You received this message because you are subscribed to the Google Groups "Sidekiq" group.
To unsubscribe from this group and stop receiving emails from it, send an email to sidekiq+u...@googlegroups.com.
To post to this group, send email to sid...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/b8fb81c1-72b6-44bc-a2b9-1bbfe5a577a9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Mike Perham – CEO, Contributed Systems

Smart, effective open source infrastructure for your apps.

[Angel Jose]

Thanks for replying. 

So I think at the time, I was trying to follow the 'Using Redis' portion of the wiki, although now that you point it out, I don't think I'd been using it correctly. :|

Re: Spring... what is that? Hadn't read anything about it in the docs?

Thanks again.

[Mike Perham]

Spring is a Rails app preloader, speeds up running your tests but also causes general mayhem, like you're reporting.

To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/82664192-fb35-4247-b427-27c78f43695a%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[Angel Jose]

I'm on Rails 3.2.13, so I'm not sure that spring is a factor then (just checked that it comes preloaded in 4+), but the symptoms sound very similar.

At one point, I did call that method from that worker, so it does sound logical that somehow it's calling from the cache, rather than the actual method. Any other suggestions? Or other files that I can post to give some clues?

Thanks.

--
You received this message because you are subscribed to a topic in the Google Groups "Sidekiq" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/sidekiq/HNAFMIKqjQQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to sidekiq+u...@googlegroups.com.

To post to this group, send email to sid...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/CAPjBv7rjZe4qTLQR46O3oNQ7scBd1Pfdfit5mUu-vNSxGxpGKA%40mail.gmail.com.

[Abhi Rao]

Angel,

What environment are you running in? The simplest explanation is that sidekiq IS running the old code. Unless you're running something like spring you will need to restart the sidekiq processes to pick up your code changes. Can you confirm that you've restarted the processes?

To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/CALHs7%3DKauAgzcg2BP2RsUf1SwPRRxGk7PyRuVZ5LWBYbPVAxxg%40mail.gmail.com.

[Mike Perham]

You need to restart Sidekiq every time you make a code change.  Sidekiq does not auto-reload code unlike the web server.

To view this discussion on the web visit https://groups.google.com/d/msgid/sidekiq/CALHs7%3DKauAgzcg2BP2RsUf1SwPRRxGk7PyRuVZ5LWBYbPVAxxg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Angel Jose]

This makes sense. I'm running in a docker environment, yet I thought when I'm stopping and restarting the containers, that would take care of it?

docker-compose stop

docker-compose up

Thanks.