-
Notifications
You must be signed in to change notification settings - Fork 34
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
Invalid “hours” in range cause cron #next_time loop breaker issue #30
Comments
https://crontab.guru/#*_0-24___* says
I should probably simply reject. But accepting 24, is lenient, à la Postel. |
Already accepting Line 50 in 12a2faa
|
Released as part of fugit 1.3.2. https://rubygems.org/gems/fugit/versions/1.3.2 Please tell me if there is anything wrong. Many thanks with this issue report. |
Thanks for the quick fix! Looking good 😄 |
Issue description
Values outside 0-23 in an hour range cause an infinite loop error.
How to reproduce
Expected behaviour
The “24” being out of range should either result in a parsing error or being treated as 0.
Context
Please replace the content of this section with the output of the following commands:
Additional context
Encountered via in-the-wild user input!
The text was updated successfully, but these errors were encountered: