Comments (5)
I changed my timezone to PDT and got:
Sat May 18 2013 05:56:37 GMT-0700 (PDT)
Mon May 20 2013 08:45:00 GMT-0700 (PDT)
Mon May 27 2013 08:45:00 GMT-0700 (PDT)
Mon Jul 01 2013 08:45:00 GMT-0700 (PDT)
Mon Jul 08 2013 08:45:00 GMT-0700 (PDT)
Mon Jul 15 2013 08:45:00 GMT-0700 (PDT)
from cron-parser.
thanks for the reply. it's quite odd... can you tell me two things:
- what platform (mac, linux, windows, etc.) you did your test on? (i'm on a mac)
- what sequence of commands you did to change the TZ before running the test?
thanks!
/mtr
from cron-parser.
- OS X (10.7)
- Date & Time Preferences -> PDT
from cron-parser.
this is quite odd. i am on 10.8.3, i have selected a closest city, it says "Time Zone: Pacific Daylight Time". (it's been set like this for four months over several reboots.)
well, since it works for you, i'll dig around in the code a bit.
thanks!
from cron-parser.
found it!
00 45 8 * * 1 = winner
00 45 08 * * 1 = loser (hour set to '0' not '8')
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.