-
The development of https://github.com/robfig/cron seems to be stopped and thus it should probably be replaced.
-
We should totally have a CRON job expression parser in our list of tools!
-
### Describe the bug
Cron expressions like `0 6 * * MON#1` are currently able to being registered, display and executed, but flytescheduler produces the following error logs:
```
unable to register…
-
### Problem
As of now the cron schedule using the command below is scheduled always in the `UTC` timezone. We have to provide the option to the user to set the timezone of their choice using the f…
-
# Bug: Incorrect next execution date calculation for "0 15 10 ? * 6#3"
## Description
I encountered a bug in cron-utils version 9.2.0 when calculating the next execution date for the cron expressi…
-
When adding Sunday as value `7` inside `daysOfWeek` of the CronFields, and later parsing it to a cron expression with `fieldsToExpression().stringify()`, it is ignored.
Following the "Manipulation"…
arwa9 updated
5 months ago
-
I'm trying to use this lib on an HTML5 web application.
After adding this lib to the project I've noticed that this the package depends on i18n, and this one depends on "fs" from node.
Is it possi…
-
It would be great if we could expand the cron expression to support one corner case, last day of a month.
https://stackoverflow.com/questions/6139189/cron-job-to-run-on-the-last-day-of-the-month…
-
# Feature Summary
## Origin Of The Problem
Assertion of cron expressions in a project is also very important, and a programmer writing a wrong cron expression in a project can even cause a disas…
-
Hi,
CronParser#next is failing with some expressions. One example:
expression = "15-59/15 \* \* \* *"
cron_parser = CronParser.new(expression)
next_execution_time = cron_parser.next(Time.now)
Trace…