You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Curious to hear your thoughts. I don't know what the consequences are of removing these casts, although no tests fail. Are these to_f's, perhaps, necessary for things to work with Sidekiq?
The text was updated successfully, but these errors were encountered:
The same error seems to happen when using SolidQueue and attempting to schedule an acidic job to occur at a later date (using set(wait: 1.minute) for example). The issue is resolved by removing the casts. Happy to submit the PR if you would accept it.
When used with GoodJob, retrying a failed job raises a NoMethodError: "undefined method `utc' for an instance of Float".
Backtrace:
Removing the
to_f
's here, fixes the problem:acidic_job/lib/acidic_job/mixin.rb
Lines 65 to 67 in f49e6b3
The overridden ActiveJob::Core#set doesn't cast the timestamps:
https://github.com/rails/rails/blob/888d28460f5bd1444eeb171cb827cd91739c3759/activejob/lib/active_job/core.rb#L165-L167
Here is a repro: https://github.com/ahacop/acidic-job-good-job-repro, with a test that demonstrates the issue.
Curious to hear your thoughts. I don't know what the consequences are of removing these casts, although no tests fail. Are these
to_f
's, perhaps, necessary for things to work with Sidekiq?The text was updated successfully, but these errors were encountered: