After running for a long time, it automatically stopped.
See original GitHub issueis my code
const timeRuleFresh = new schedule.RecurrenceRule();
timeRuleFresh.second = [1, 6, 11, 16, 21, 26, 31, 36, 41, 46, 51, 56];
const j = schedule.scheduleJob(timeRuleFresh, async () => {
const ret = await redis.lock('LOCK_REFRESH_WIDGET', 4);
if (ret) {
await refresh();
}
});
will don’t work, when i run long time(25d),Happed twice,not every error info
Issue Analytics
- State:
- Created 5 years ago
- Reactions:3
- Comments:7
Top Results From Across the Web
Losing Running Fitness: A Scientific Look at How Much You'll ...
After 7-10 days of not running, you will lose some muscle power and coordination, but not enough to totally derail your goals. With...
Read more >How does stopping mid-run impact your training?
A better alternative to prolonged breaks and stops during a long run or workout is to add walking segments as needed.
Read more >5 Reasons Your Vehicle's Engine May Stall While You're Driving
After all, braking too hard while the clutch is engaged can cause the car to stall, as can disengaging the clutch too quickly....
Read more >Computer Restarts or Shuts Down Intermittently, Locks Up ...
This article provides recommendations to resolve an issue with your Dell computer restarting, shutting down, locking up or not responding, ...
Read more >Windows doesn't respond or stops working on Surface
Surface Devices Surface More...Less. Windows 11Windows 10.. If Windows starts up slowly, runs slowly, or stops responding (freezes) on your Surface, ...
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
It seems this is a bug that was fixed in Node 10.9.0 https://github.com/nodejs/node/issues/22149
@eharrow Hmm, I guess you could check if your current node version is >= 10.0 and < 10.9 and in that case set a timer for like 24 days and cause the service to restart when that timer fires.