This repository has been archived by the owner on Apr 1, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 121
Rails 4.2 ActiveJob job id mismatch #122
Comments
What version of the gem did you run this against? |
Thanks for the report! I'll try digging into the best fix for this when I have some free time. Ideally, it would be nice to see this working properly in Rails 4.2 environments. Could I ask you to also post how you launched the job and/or steps to reproduce? |
My fix is a backport of this PR for rails 5: rails/rails#25961 I will try to write some specs to reproduce this issue. |
I got the
Not efficient if there are many jobs on the queue, since it's a linear search. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In rails 4.2 the job status is reported to the sidekiq job id and the progress ends up at the ActiveJob job id resulting in two status lines in the webinterface. This should have been fixed by
privider_job_id
. Unfortunatelyprovicer_job_id
is broken in Rails 4.2.I put the folliwing code in
config/initializers/active_job_provider_job_id.rb
to fix it:The text was updated successfully, but these errors were encountered: