-
Notifications
You must be signed in to change notification settings - Fork 264
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
Unix crontab nextExecution bug #45
Comments
@mjsaber Thank you for reporting this. We are working on a solution right now. Will keep you posted about updates on this issue. |
This issue exposes bad next/previous execution calculation as well as the fact that predicted time is always computed in local timezone, not in same timezone as reference date. |
…ts are now returned in same timezone as reference date.
@mjsaber the issue was fixed! Will release a new version with the fixes before weekend. |
@mjsaber Version 3.1.1 was released including this fix! |
I'm trying a simple unix crontab "* * * * 1", which should run every minute of every hour Mondays in every month, but nextExecution doesn't seem give the correct result. Following is the code:
Output:
now:2015-10-13T17:26:54.468-07:00
next execution:2015-11-02T00:00:00.000-08:00
last execution:2015-10-05T23:59:00.000-07:00
The last execution time seems correct, but next execution time should be 2015-10-19T00:00:00.000-07:00. It skips two weeks and also change the time zone. Can you guys take a look at it?
Thanks,
Jun
The text was updated successfully, but these errors were encountered: