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
Hello, thanks for the project, I have used it for a while and it help me a lot.
I didn't think much about day light saving before because I live in a country without it.
But now, I'm working on a project used in America and Europe, so I have to deal with it.
I find that when dst starts, the cron may not fire the job and fire the next day.
For example, if I have a job at 2:30, and the dst starts with 01:59:00->03:00:00, then it will skip the day. And if I have a job at 1:30, and the dst ends with 01:59:59->01:00:00, then it will fire twice.
Actually, I don't know what the proper behavior is. What about your alarm clock's behavior on your phone?
Can we have some config to change the behavior ?
The text was updated successfully, but these errors were encountered:
And I've found some linux cron's behavior. If I have a job at 2:30, and dst starts with 01:59:00->03:00:00,it will fire at 03:00:00.(I think it's still a little surprising) And it won't fire twice when dst ends.
with #639 we had some refactoring done with daylight savings jobs. could you see if that resolved your issue? if not, could you make a test case demonstrating the error? we have several tests for daylight savings already that should be similar to your use case
Hello, thanks for the project, I have used it for a while and it help me a lot.
I didn't think much about day light saving before because I live in a country without it.
But now, I'm working on a project used in America and Europe, so I have to deal with it.
I find that when dst starts, the cron may not fire the job and fire the next day.
For example, if I have a job at 2:30, and the dst starts with 01:59:00->03:00:00, then it will skip the day. And if I have a job at 1:30, and the dst ends with 01:59:59->01:00:00, then it will fire twice.
Actually, I don't know what the proper behavior is. What about your alarm clock's behavior on your phone?
Can we have some config to change the behavior ?
The text was updated successfully, but these errors were encountered: