-
Notifications
You must be signed in to change notification settings - Fork 105
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Support for year in Croniter #76
Comments
+1 |
No, seconds is not the 6th part. |
Hang on, why is this closed.. First of all:
Prints:
Sure looks like the 6th element is seconds to me. If it isn't, please clarify.. And also I'm confused why the year request was just disregarded if there are seconds. Then again, if seconds support is a bug... (which I rely on btw). |
Even I'm not sure why this was closed. Standard cron doesn't take year into account. So I thought it would be a new feature request. Apart from that you're correct. This library treats the sixth field of a cron pattern as second. |
Docs: http://www.nncron.ru/help/EN/working/cron-format.htm
|
croniter mostly sticks with the original 5fields cron format with some variations. There are some bits with 6fields (seconds): https://github.com/taichino/croniter#about-second-repeats but not a full support. PR are welcomes ;-) |
I want to execute a job at
6 AM on 2nd, Feb 2018
only once. The corresponding cron expression would be"0 6 2 2 * 0 2018"
.In croniter, seconds is the 6th part of the cron expression. But I am getting
CroniterBadError
when I try to provideyear
also. Is there any way to accomplish this. Or this might be a new feature request.The text was updated successfully, but these errors were encountered: