You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the croneval CLI tool, this spits an error to a perfectly valid one-time cron expression (tested on 6.3.2)
./bin/elasticsearch-croneval "0 3 23 8 9 ? 2019"
Valid!
Now is [Thu, 9 Aug 2018 07:54:34]
Here are the next 10 times this cron expression will trigger:
1. Mon, 9 Sep 2019 01:03:00
ERROR: 2. Could not compute future times since [Mon, 9 Sep 2019 01:03:00] (perhaps the cron expression only points to times in the past?)
Instead of printing an error, we should just print the first line and exit and be good, as a one time cron expression is perfectly fine.
The text was updated successfully, but these errors were encountered:
CronEvalTool prints an error only for cron expressions that result in
no coming time events.
If a cron expression results in less than the specified `-count`
(default 10) time events, the CronEvalTool prints all the coming
times and displays no error message.
Fixeselastic#32735
CronEvalTool prints an error only for cron expressions that result in
no upcoming time events.
If a cron expression results in less than the specified count
(default 10) time events, now all the coming times are printed
without displaying error message.
Closes#32735
CronEvalTool prints an error only for cron expressions that result in
no upcoming time events.
If a cron expression results in less than the specified count
(default 10) time events, now all the coming times are printed
without displaying error message.
Closes#32735
Using the
croneval
CLI tool, this spits an error to a perfectly valid one-time cron expression (tested on 6.3.2)Instead of printing an error, we should just print the first line and exit and be good, as a one time cron expression is perfectly fine.
The text was updated successfully, but these errors were encountered: