Bug with schedule object literal syntax
See original GitHub issueWhen I described schedule like this:
scheduleJob({ second: [0, 10, 20, 30, 40, 50] }, ...
// or
scheduleJob({ minute: [1, 11, 21, 31, 41, 51] }, ...
Sometimes job function called twice at the same schedule time.
It happens rarely. Also i didn’t notice this issue with string syntax:
scheduleJob('*/10 * * * * *', ...
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Why am I getting an error "Object literal may only specify ...
Usually this error means you have a bug (typically a typo) in your code, or in the definition file. The right fix in...
Read more >927649 - for-of iterator result should use object literal syntax instead ...
As discussed in bug 907077 comment 78 and comment 80 the es6 for-of iterator implementation should use object literal syntax instead of Object.create(null)....
Read more >JavaScript Object Literal Syntax Extension in ES6 By Examples
This tutorial shows you how to use new object literal syntax extensions including property initializer shorthand, computed properties, and concise method.
Read more >SyntaxError: unterminated string literal
SyntaxError : Unterminated string constant (Edge) SyntaxError: ... String literals must be enclosed by single ( ' ) or double ( " )...
Read more >Getting Literal With ES6 Template Strings - Chrome Developers
Template String literals with embedded expressions. ... Syntax. Template Strings use back-ticks (``) rather than the single or double quotes ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@AlexVoitenko can you try with the lastest version (
1.3.0
). it should be fixed there. In case it’s not, let me know. Thanks!Good to know