-
Notifications
You must be signed in to change notification settings - Fork 948
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
odd daylight saving behaviour #598
Comments
Hi There,
The output from this is:
Which as you can see doesn't have the expected next run time or idle time for the first example, which is one week before daylight saving ends. |
I have a job I want to schedule every day at a particular time UTC.
Running at 10:59 local time (which is Pacific/Auckland - currently UTC+12) I get the following output:
This shows the bug highlighted in issue #579 with it skipping the closest 00:00UTC.
If I change the schedule to
schedule.every().monday.at("00:00", "Etc/UTC").do(job)
Then I get the following output
As you can see, it is now scheduling the job for 13:00 local time. However it should be 12:00 local time because we are currently UTC+12. This behaviour started yesterday (Sunday). Prior to that it would schedule the job at the correct time. So it looks like somewhere daylight saving time is being incorrectly applied a week early (my local timezone shifts to daylight saving [UTC+13] next Sunday). But this is only happening with schedule.every().weekday and not schedule.every().day
The text was updated successfully, but these errors were encountered: