Closed donkeybridge closed 2 years ago
From man 5 crontab
:
Note: The day of a command's execution can be specified by two fields —
day-of-month and day-of-week. If both fields are restricted (i.e. aren't
*), the command will be run when either field matches the current time.
For example,
30 4 1,15 * 5
would cause a command to be run at 4:30 am on the 1st and 15th of each
month, plus every Friday.
As seen in gh-5 and gh-35.
See also https://crontab.guru/#0_0_29_2_0,6
Not closing yet, I want to investigate
Fugit::Cron.parse('0 0 11 * 3-6').next_time.strftime('%a, %Y-%m-%d') # SIC!
# => "Wed, 2021-12-29"
Fugit::Cron.parse('0 0 11 * 3-6').next_time.strftime('%a, %Y-%m-%d') # SIC!
# => "Wed, 2021-12-29"
Same. https://crontab.guru/#0_0_11_*_3-6
I wish you a happy new year!
ref gh-78
Issue description
I started to search for the next occurence of Feb 29th during weekend, what resulted in Sat, 2021-02-05. Further experiments showed a some gap in interpreting cron strings.
How to reproduce
At first I was guessing this related to leap day, but unfortunately it got worse:
Error and error backtrace (if any)
Expected behaviour
Context
Please replace the content of this section with the output of the following commands:
Additional context