-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
Schedule next_run does not take daylight savings time into account #4025
Comments
This should depend on your system time. |
The system time is correct, now the schedules are running normally, but if the previous schedule ran without DST, then the next would run +1 hour later, after that everything is normal |
Seems more like a bug with the cron library. I don't actually have any particularly special logic that would be the culprit. Lines 133 to 140 in 14cc98f
|
Apparently not a bug - mtdowling/cron-expression#116 |
Guessing it might be a bug that was long fixed in https://github.com/dragonmantank/cron-expression which is the actual library we use, in which case it will likely end up fixed in coming weeks as we update dependencies and push out those changes. |
Was this ever looked into / resolved? I'm still seeing this myself in Schedules. You can see these are actually offset by an hour, and have been since Daylight Savings changed on 03/12/2023. |
Current Behavior
Currently, due to the change to daylight savings time, every schedule that was previously executed yesterday was executed an hour later.
I am guessing it happens because next_run_at is being set when the previous schedule executes, causing the resulting date to not include DST.
Expected Behavior
The schedule should be executed at the same time every time.
Maybe make next_run_at use UTC, so there won't be any problems with DST (make getNextRunDate return UTC, and instead of NOW() use UTC_TIMESTAMP())?
Steps to Reproduce
Panel Version
1.7.0
Wings Version
1.6.1
Games and/or Eggs Affected
No response
Docker Image
No response
Error Logs
No response
Is there an existing issue for this?
The text was updated successfully, but these errors were encountered: