-
Notifications
You must be signed in to change notification settings - Fork 33
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
cron #previous_time loop breaker issue: modulo plus offset #47
Comments
Thanks a ton for the report! Give me a few days to ponder a better interception/information. Year end crunch :-( |
Sorry, I forgot about this one. One of your contractors reminded me of it. I will look into it again. |
I think I solved the problem. I will release 1.4.5 tomorrow, unless you point me at corner cases I have overlooked. Please accept my apologies for forgetting your issue. cc @karensawrey |
Released 1.4.5 Thanks a lot! |
Thank you, @jmettraux! Highly appreciated! Thank you kindly for working on fugit and for dedicating your time to solving this issue. |
All good @jmettraux, I very much appreciate your help on these! :) |
Issue description
I am not fully confident in what the combination of these two syntaxes is supposed to mean, and the +2 syntax isn’t documented fully in the README, but I believe this user input would be interpreted as every odd Tuesday but only after the first two odd Tuesdays of a month? Which seems to mean “never,” and thus warrant an out of range error.
How to reproduce
Error and error backtrace (if any)
(This should look like:
)
Expected behaviour
It ought to either return a valid value, or give a descriptive error rather than the loop error.
Context
Additional context
Like #30, this is from in-the-wild user input. 😃
The text was updated successfully, but these errors were encountered: