profile
viewpoint

kelektiv/node-cron 6285

Cron for NodeJS.

kelektiv/node.bcrypt.js 5144

bcrypt for NodeJs

startedkelektiv/node.bcrypt.js

started time in an hour

startedkelektiv/node-cron

started time in an hour

startedkelektiv/node.bcrypt.js

started time in 3 hours

startedkelektiv/node-cron

started time in 3 hours

startedkelektiv/node.bcrypt.js

started time in 15 hours

startedkelektiv/node-cron

started time in 15 hours

startedkelektiv/node-cron

started time in 17 hours

startedkelektiv/node-cron

started time in 18 hours

issue commentkelektiv/node.bcrypt.js

dyld: lazy symbol binding failed: Symbol not found

I just updated node to the latest version 13.x and that solved it for me :)

nornagon

comment created time in 19 hours

startedkelektiv/node.bcrypt.js

started time in 21 hours

startedkelektiv/node.bcrypt.js

started time in a day

startedkelektiv/node.bcrypt.js

started time in a day

startedkelektiv/node-cron

started time in a day

startedkelektiv/node.bcrypt.js

started time in a day

startedkelektiv/node.bcrypt.js

started time in 2 days

startedkelektiv/node.bcrypt.js

started time in 2 days

startedkelektiv/node-cron

started time in 2 days

startedkelektiv/node-cron

started time in 2 days

startedkelektiv/node-cron

started time in 2 days

startedkelektiv/node.bcrypt.js

started time in 3 days

startedkelektiv/node-cron

started time in 3 days

startedkelektiv/node-cron

started time in 3 days

startedkelektiv/node-cron

started time in 3 days

startedkelektiv/node.bcrypt.js

started time in 4 days

startedkelektiv/node-cron

started time in 4 days

startedkelektiv/node.bcrypt.js

started time in 4 days

startedkelektiv/node.bcrypt.js

started time in 4 days

startedkelektiv/node-cron

started time in 5 days

startedkelektiv/node-cron

started time in 5 days

startedkelektiv/node-cron

started time in 5 days

startedkelektiv/node.bcrypt.js

started time in 5 days

startedkelektiv/node-cron

started time in 5 days

startedkelektiv/node.bcrypt.js

started time in 5 days

startedkelektiv/node-cron

started time in 5 days

fork panxiande/node-cron

Cron for NodeJS.

fork in 5 days

startedkelektiv/node-cron

started time in 5 days

startedkelektiv/node.bcrypt.js

started time in 6 days

issue closedkelektiv/node-cron

Timezone error

Hi. I try to use timezones to run tasks and receive the error: couldn't start the job: 13: Error: Unknown Timezone: 'America/Los_Angeles' Could you help my pleas?

closed time in 6 days

Bortnyak

issue openedkelektiv/node-cron

Timezone error

Hi. I try to use timezones to run tasks and receive the error: couldn't start the job: 13: Error: Unknown Timezone: 'America/Los_Angeles' Could you help my pleas?

created time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

issue commentkelektiv/node.bcrypt.js

Pre-built binaries not found for bcrypt@3.0.6 and node@12.2.0 (node-v72 ABI, unknown)

I had a similar issue:

node-pre-gyp WARN Using request for node-pre-gyp https download
node-pre-gyp WARN Tried to download(404): 
https://github.com/kelektiv/node.bcrypt.js/releases/download/v3.0.4/bcrypt_lib-v3.0.4-node-v72- 
linux-x64-glibc.tar.gz
node-pre-gyp WARN Pre-built binaries not found for bcrypt@3.0.4 and node@12.16.1 (node-v72 
ABI, glibc) (falling back to source compile with node-gyp)

This issue arises mainly because of different global and local versions of node and that the node-gyp compilation happens with the node installed globally on your system for which the pre-built binaries are not available.

Solution

The solution is to install a global (possibly earlier) version of node for which the prebuilt binaries for node-gyp is available.

RyleeAndrews

comment created time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node-cron

started time in 7 days

startedkelektiv/node.bcrypt.js

started time in 7 days

startedkelektiv/node.bcrypt.js

started time in 7 days

startedkelektiv/node.bcrypt.js

started time in 8 days

startedkelektiv/node.bcrypt.js

started time in 8 days

startedkelektiv/node.bcrypt.js

started time in 8 days

startedkelektiv/node.bcrypt.js

started time in 8 days

startedkelektiv/node-cron

started time in 8 days

startedkelektiv/node-cron

started time in 8 days

startedkelektiv/node.bcrypt.js

started time in 9 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations

agree, happens when load goes high

mtjn

comment created time in 9 days

issue commentkelektiv/node-cron

Something went wrong. cron reached maximum iterations

I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.

fabnavigator

comment created time in 9 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations.

I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.

MilyaushaShigapova

comment created time in 9 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations.

I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.

AfanasievN

comment created time in 9 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations

I realized the error would show whenever my CPU utilization is too high (>9x%). That might cause some delay of code and affect something.

mtjn

comment created time in 9 days

issue commentkelektiv/node.bcrypt.js

mkdirp@0.5.3: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

I am also getting same messagae: For my new laptop fassing issue while trying to install React Native. Processing template × Installing dependencies error Error: Command failed: npm install npm WARN deprecated mkdirp@0.5.4: Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)

image

ridoy19

comment created time in 9 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations

Same. I am also using cron@1.8.2.

mtjn

comment created time in 9 days

issue commentkelektiv/node-cron

cron reached maximum iterations

It is not solved. I am using version 1.8.2 and still get the same error.

bradleyy1012

comment created time in 9 days

issue commentkelektiv/node-cron

Something went wrong. cron reached maximum iterations

It keeps getting referenced to, so is this fixed or not? I encountered this just today. Is there a solution?

fabnavigator

comment created time in 9 days

startedkelektiv/node.bcrypt.js

started time in 9 days

startedkelektiv/node.bcrypt.js

started time in 10 days

fork Nicoxx45/node-cron

Cron for NodeJS.

fork in 10 days

startedkelektiv/node-cron

started time in 10 days

fork Tyav/node-cron

Cron for NodeJS.

fork in 10 days

startedkelektiv/node-cron

started time in 10 days

issue commentkelektiv/node-cron

cron fails on two servers, approximately same time, without error

This morning I got this same error and tried out with a fresh new install of rasbian and node-red. I was able to pinpoint it to an inject node with specific content. With this (below) node it crashed, with other configurated inject nodes there are no problems.

[{"id":"a02e32cd.28c53","type":"tab","label":"Flow 6","disabled":false,"info":""},{"id":"a78a0f31.f1bc9","type":"inject","z":"a02e32cd.28c53","name":"Init & reset","topic":"","payload":"auto","payloadType":"str","repeat":"","crontab":"*/20 2 * * *","once":true,"onceDelay":0.1,"x":130,"y":120,"wires":[[]]}]

ChristophDFine

comment created time in 11 days

issue commentkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations

yes, it reappeared, though solved in 1.7 one year ago

cron@1.8.2

Error: Something went wrong. cron reached maximum iterations. 						
Please open an  issue (https://github.com/kelektiv/node-cron/issues/new) and provide the following string 	
					
Time Zone: "" - Cron String: 39 0,15,30,45 * * * * - UTC offset: +00:00 - current Date: Sat Mar 28 2020 13:30:45 GMT+0000     

at CronTime._getNextDateFrom (/app/node_modules/cron/lib/cron.js:235:12)     
at CronTime.sendAt (/app/node_modules/cron/lib/cron.js:156:17)     
at CronTime.getTimeout (/app/node_modules/cron/lib/cron.js:175:29)     at CronJob.start (/app/node_modules/cron/lib/cron.js:613:31)     
at Timeout.callbackWrapper [as _onTimeout] (/app/node_modules/cron/lib/cron.js:665:29)     
at listOnTimeout (internal/timers.js:531:17)     
at processTimers (internal/timers.js:475:7)
mtjn

comment created time in 11 days

startedkelektiv/node-cron

started time in 12 days

startedkelektiv/node-cron

started time in 12 days

startedkelektiv/node-cron

started time in 12 days

startedkelektiv/node.bcrypt.js

started time in 12 days

startedkelektiv/node-cron

started time in 12 days

startedkelektiv/node.bcrypt.js

started time in 12 days

issue commentkelektiv/node.bcrypt.js

dyld: lazy symbol binding failed: Symbol not found

I forgot to nvm use. It was installed with a different version of Node than the default system Node.

nornagon

comment created time in 12 days

startedkelektiv/node-cron

started time in 13 days

startedkelektiv/node-cron

started time in 13 days

startedkelektiv/node.bcrypt.js

started time in 13 days

issue commentkelektiv/node-cron

Wait for job finished to execute the next one

This is working fine for me const job = cron.schedule('*/10 * * * * *', async function(){ job.stop(); filter = 'PENDING', slidingTime = 60 await heatmap_settings.findOne().select('options filterType').then(setting => { filter = setting.filterType slidingTime = setting.options.slidingTime }).catch(err => console.log(err)) await getHeatmapRules() job.start(); }, { scheduled: true })

qeude

comment created time in 13 days

startedkelektiv/node.bcrypt.js

started time in 13 days

startedkelektiv/node.bcrypt.js

started time in 13 days

issue commentkelektiv/node.bcrypt.js

Expected in: flat namespace

@XWindMan Can you please report your exact NodeJS version?

XWindMan

comment created time in 13 days

startedkelektiv/node-cron

started time in 13 days

pull request commentkelektiv/node-cron

Json parameter parsing

Just a heads up, I haven't forgotten about this. I've just been insanely busy. I'll be reviewing this when I get a chance. Thanks for the effort on it.

lperanni

comment created time in 14 days

more