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
I just have a general question. Does clockwork cater for changes to the time by way of daylight savings? So for example you have a database driven schedule (checking for updates every minute) and one of the database rows has a timezone of Pacific/Auckland, to run every week on a Sunday at 3am.
When daylight savings rolls around and the clocks are turned backwards from 3am to 2am, is the scheduled event going to happen at the old 3am (which is now 2am) or the new 3am?
@chukkwagon no I never got an answer but as far as I can tell it doesn't cater to daylight savings changes so I just have a regular cron that runs every minute, checks all records to see if there any that match the current day of the week / time and then spawns a new queued job to run the task if there are any matches.
Thanks for getting back to me. Interestingly, I do not believe that the following snippet is amenable to DST cutover for daily periods that specify an at argument.
Activity
chukkwagon commentedon Mar 11, 2019
@JamesPlayer did you ever find an answer to this question?
JamesPlayer commentedon Mar 12, 2019
@chukkwagon no I never got an answer but as far as I can tell it doesn't cater to daylight savings changes so I just have a regular cron that runs every minute, checks all records to see if there any that match the current day of the week / time and then spawns a new queued job to run the task if there are any matches.
chukkwagon commentedon Mar 12, 2019
Thanks for getting back to me. Interestingly, I do not believe that the following snippet is amenable to DST cutover for daily periods that specify an
atargument.clockwork/lib/clockwork/event.rb
Lines 64 to 66 in b6baf3e
For a 24 hour period (3am Sunday to 3am monday) daily jobs will not run because the maximum time elapsed will be 23 hours.