Comments (2)
Hi,
Sorry to hear that you had an issue with that. In the readme there is explicitly mentioned that seconds field is optional field. If you're not providing second field, it's working like specified in crontab standard, and if you're providing value for second field, it works in extended mode.
Can you provide me exact example which caused an issue?
BR,
Harri
from cron-parser.
thanks for the kind reply @harrisiirak .I noticed that the docs specify seconds, unfortunately I noticed that only after I had the bug.. a quick visual look at the github page shows a drawing very similar to all cron descriptions, but the rest don't have seconds.. that's why I missed that!. the basic problem was I was passing 15 23 * *
1-5 (23:15 monday-friday) so I had an extra
` in the end of the cron expression. most cron implementations would shout at me or at least issue a warning. (btw I'm not using directly but tried to debug node-schedule and the found the bug here)
from cron-parser.
Related Issues (20)
- cron job get stopped with no error automatically HOT 5
- Use es6 modules (error: module undefined) HOT 2
- Stringify argument not documented.
- fields.dayOfWeek = [1,3,5] generates incorrect cron expression HOT 5
- Example in README is incorrect HOT 1
- v4.8.0 fields.dayOfWeek = [1,3,5,6] generates incorrect cron expression HOT 1
- parseExpression('') returns valid CronExpression HOT 1
- Time zone formatting not working as expected HOT 1
- parseString方法处理spring格式的cron时生成的fields错位了
- Pull Request? HOT 4
- suggestion for iterator example
- Yes, I've also seen it quite frequently in the past. More fun (and actually practical) reasoning behind naming conventions: https://stackoverflow.com/a/41967120/143788 HOT 1
- cron expression does not match result HOT 2
- Add nthDayOfMonth examples
- Unexpected behavior with hours range HOT 1
- ”0 0 22 * * ? * “ parser cron expression error HOT 2
- Unexpected behavior when the step size plus the starting value is higher than the maximal expected value HOT 1
- :bug: the cron time is error HOT 1
- Incorrect next time in UTC for cron expression in America/New_York timezone HOT 9
- The crontab expression '0 0 0 12W 6' is causing a parsing error HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from cron-parser.