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
When adopting the new bulk enqueue feature, we noticed that scheduled_at was getting removed from jobs. This would lead to very high spikes in load, because all the wait values we would specify would just end up getting discarded.
When I examine the code, I see that the issue is in the build_for_enqueue method. It takes the attributes of the active job verbatim, but for some reason the scheduled_at at the ActiveJob level is a Float, not a Time. This scheduled_at value (still a Float) then gets passed to Execution.new and it gets discarded - because the datatype is not correct.
For the moment I seem to be able to circumvent this with the following patch:
but it is not entirely clear to me where the conversion from the Float (which seems to be ActiveJob-native) to the Time should take place. it is evident the conversion does need to happen somewhere though
The text was updated successfully, but these errors were encountered:
When adopting the new bulk enqueue feature, we noticed that
scheduled_at
was getting removed from jobs. This would lead to very high spikes in load, because all thewait
values we would specify would just end up getting discarded.When I examine the code, I see that the issue is in the
build_for_enqueue
method. It takes the attributes of the active job verbatim, but for some reason thescheduled_at
at the ActiveJob level is aFloat
, not aTime
. Thisscheduled_at
value (still a Float) then gets passed toExecution.new
and it gets discarded - because the datatype is not correct.For the moment I seem to be able to circumvent this with the following patch:
but it is not entirely clear to me where the conversion from the
Float
(which seems to be ActiveJob-native) to theTime
should take place. it is evident the conversion does need to happen somewhere thoughThe text was updated successfully, but these errors were encountered: