-
-
Notifications
You must be signed in to change notification settings - Fork 277
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
perform_in not working in version 4.0.9 #150
Comments
It should be safe to upgrade Sidekiq but apparently you are running into some problem with it. Are you certain your jobs are being processed? I mean are your workers really doing its thing? Sidekiq now needs more connections to redis for workers. Could that be related maybe? |
Yea Sidekiq upgrade went fine, plenty of room for connections, so I don't think that's the issue. via mobile device, please excuse typos and terseness.
|
And sorry I meant is it safe to upgrade to |
I had similar issue when using activejob with sidekiq test task class UniquenessTest < ActiveJob::Base
def perform num
10.times do |i|
puts "#{num} #{i}"
sleep 1
end
end
end set sidekiq output when i run
sidekiq output when i run
|
It seems that by design of Stacktrace for task started by
Stacktrace for task started by
|
@kapso did you find any solution? I'm running into the same problem. I could solve it only by downgrading to 4.0.7. |
No solution yet. |
Sorry guys, I've completely forgotten about this issue. I'll try and fix it first thing tomorrow. |
What is inside |
I am running |
Both
perform_in
andperform_at
are not working.perform_async
does work.I am running version
4.0.9
with Sidekiq version 4.0.1, Redis version 2.8.3When I run the following code, perform method does not get executed
I am running into so many issues when upgrading to
sidekiq-unique-jobs v4
, think I have opened few tickets already, is it safe to upgrade to v4 or best to run v3?The text was updated successfully, but these errors were encountered: