Skip to content
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

Why does get_next() return a real day for the incorrect cron expression? ('0 0 0 1 0') #9

Closed
leemurus opened this issue Jan 11, 2022 · 2 comments

Comments

@leemurus
Copy link

On wikipedia, day cannot be 0. https://en.wikipedia.org/wiki/Cron. Why do you allow?

@kiorky kiorky closed this as completed Jan 14, 2022
@kiorky kiorky reopened this Jan 14, 2022
@kiorky
Copy link
Collaborator

kiorky commented Jan 14, 2022

related to #6, seees there is another cornercase, i'm looking at it.

kiorky added a commit that referenced this issue Jan 14, 2022
This relates #9
@kiorky
Copy link
Collaborator

kiorky commented Jan 14, 2022

it's not for days but to support seconds repeat where in this case, fields are then shifted up to 6 and the 4th field becomes the day one.

As this case is pretty straightforward, i added some rule to check in in the new released croniter==1.2.0

Believe me, cron corner cases are infinite and using misformed crontabs expression will still always give you opportunity for bad ranges.

@kiorky kiorky closed this as completed Jan 14, 2022
kiorky added a commit that referenced this issue Dec 16, 2024
This relates #9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants