profile
viewpoint

kelektiv/node-cron 6696

Cron for NodeJS.

kelektiv/node.bcrypt.js 5479

bcrypt for NodeJs

issue commentkelektiv/node.bcrypt.js

Application is interrupted without to say anything (NodeJs 12.13.1)

Same problem here - looks like the README say they do not have binaries for Alpine.

gapinto

comment created time in 5 hours

startedkelektiv/node.bcrypt.js

started time in 5 hours

GollumEvent

startedkelektiv/node-cron

started time in 9 hours

startedkelektiv/node-cron

started time in 16 hours

startedkelektiv/node-cron

started time in a day

startedkelektiv/node-cron

started time in a day

startedkelektiv/node-cron

started time in 2 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 3 days

startedkelektiv/node-cron

started time in 3 days

issue closedkelektiv/node-cron

how can i await for job to be done ?

i need to get response from api , i need to await for job (run on init ) then go continue

closed time in 3 days

Bahramibh

issue commentkelektiv/node.bcrypt.js

Error: Cannot find module '...../bcrypt/lib/binding/napi-v3/bcrypt_lib.node'

node-pre-gyp install --fallback-to-build.. solved my issue too thanks

jellohouse

comment created 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 4 days

fork ChoMPi0/node-cron

Cron for NodeJS.

fork in 4 days

startedkelektiv/node-cron

started time in 4 days

issue commentkelektiv/node.bcrypt.js

Problem using compare when hashed password comes from database

@Webeon I'm using bcryptjs and facing the same issue. Tried everything mentioned above and nothing was wrong.

freis

comment created time in 5 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-cron

started time in 5 days

startedkelektiv/node-cron

started time in 6 days

startedkelektiv/node-cron

started time in 6 days

issue closedkelektiv/node.bcrypt.js

Feature request: calibrate salt_rounds

The bcrypt-ruby gem has a function called calibrate(max_time) (doc) which return the max salt_rounds to hash a password in less than max_time.

This feature is very useful to get the best salt_rounds on your running server.

Is it possible to add the same function ?

closed time in 6 days

Koala-gentil

issue openedkelektiv/node.bcrypt.js

Feature request: calibrate salt_rounds

The bcrypt-ruby gem has a function called calibrate(max_time) (doc) which return the max salt_rounds to hash a password in less than max_time.

This feature is very useful to get the best salt_rounds on your running server.

Is it possible to add the same function ?

created time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 days

startedkelektiv/node-cron

started time in 6 days

startedkelektiv/node.bcrypt.js

started time in 6 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 7 days

startedkelektiv/node-cron

started time in 7 days

fork flopal/node-cron-1

Cron for NodeJS.

fork in 7 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 8 days

startedkelektiv/node-cron

started time in 8 days

startedkelektiv/node.bcrypt.js

started time in 8 days

startedkelektiv/node-cron

started time in 8 days

fork Mu-L/node-cron

Cron for NodeJS.

fork in 9 days

startedkelektiv/node.bcrypt.js

started time in 9 days

startedkelektiv/node-cron

started time in 9 days

startedkelektiv/node-cron

started time in 9 days

issue commentkelektiv/node-cron

How to kill a scheduled cron job ?

@kamleshkarwande You get the reference to the job in two ways. Either by setting a variable when instantiating var a = new Job() and then calling a.stop() via a closure or something else OR by not using an arrow function for the onTick in which case the scope of the function should be the job.

Hope that helps.

How can we save a in the database. So we can do some action on this job later?

tgreco

comment created time in 9 days

startedkelektiv/node-cron

started time in 9 days

startedkelektiv/node.bcrypt.js

started time in 9 days

startedkelektiv/node.bcrypt.js

started time in 9 days

startedkelektiv/node.bcrypt.js

started time in 10 days

startedkelektiv/node-cron

started time in 10 days

startedkelektiv/node.bcrypt.js

started time in 10 days

issue commentkelektiv/node-cron

how can i await for job to be done ?

Read here the documentation: https://github.com/kelektiv/node-cron#api You can configure a callback onComplete on each tick. May this solves your requirement.

Bahramibh

comment created time in 10 days

issue commentkelektiv/node-cron

Stopping a cron after one-time execution

You don't need to do any cleanup if you specify a date object (Date/moment). But, if you specify a crown syntax you're hen you would need to use .stop(). The internal job uses setTimeout.

On Mon, Sep 14, 2020, 2:42 PM Matthias Baldi notifications@github.com wrote:

I don't know if you have to call the stop() method. But why do you create not just a simple method with a setTimeout? would be do the same thing isn't it? In my understanding a cronjob is something which runs multiple times.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/kelektiv/node-cron/issues/525#issuecomment-692240355, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAPJFZVRXATS72SKEVVV2LSFZPYVANCNFSM4Q6XJZHA .

grp06

comment created time in 10 days

issue commentkelektiv/node-cron

Stopping a cron after one-time execution

I don't know if you have to call the stop() method. But why do you create not just a simple method with a setTimeout? would be do the same thing isn't it? In my understanding a cronjob is something which runs multiple times.

grp06

comment created time in 10 days

startedkelektiv/node.bcrypt.js

started time in 10 days

startedkelektiv/node-cron

started time in 10 days

startedkelektiv/node.bcrypt.js

started time in 10 days

startedkelektiv/node-cron

started time in 10 days

startedkelektiv/node.bcrypt.js

started time in 10 days

startedkelektiv/node-cron

started time in 10 days

issue openedkelektiv/node-cron

type definitions out of date

image

created time in 11 days

startedkelektiv/node.bcrypt.js

started time in 11 days

startedkelektiv/node.bcrypt.js

started time in 11 days

startedkelektiv/node.bcrypt.js

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

issue commentkelektiv/node.bcrypt.js

process.dlopen(module, path.toNamespacedPath(filename))

for me, it was working fine but only did this when I tried to put it on Heroku(a hosting website) to fix it I just delete node_modules this will only work if what you host with will auto download your modules

webPpei

comment created time in 12 days

startedkelektiv/node.bcrypt.js

started time in 12 days

startedkelektiv/node.bcrypt.js

started time in 12 days

startedkelektiv/node.bcrypt.js

started time in 13 days

startedkelektiv/node.bcrypt.js

started time in 13 days

pull request commentkelektiv/node-cron

Migrate from Moment.js to Luxon

When it will be published?

bvigursky

comment created time in 13 days

IssuesEvent

issue closedkelektiv/node.bcrypt.js

ReferenceError: bcrypt is not defined

Dear All, I'm a beginner in web development. I can't resolve such problem: I can't use my bcrypt package because when I'm running my app I have such error: ReferenceError: bcrypt is not defined

I have done the installation of: $ npm install --global --production windows-build-tools then I have done the installation: $ npm install bcrypt and I've got: + bcrypt@5.0.0 added 68 packages from 100 contributors and audited 68 packages in 8.563s

But when I'm trying to see the bcrypt version in my terminal I have an error: $ bcrypt --version bash: bcrypt: command not found

and when I'm running my app I can't use bcrypt. Could you give me advice, please?

closed time in 14 days

Yuliashka

issue openedkelektiv/node.bcrypt.js

ReferenceError: bcrypt is not defined

Dear All, I'm a beginner in web development. I can't resolve such problem: I can't use my bcrypt package because when I'm running my app I have such error: ReferenceError: bcrypt is not defined

I have done the installation of: $ npm install --global --production windows-build-tools then I have done the installation: $ npm install bcrypt and I've got: + bcrypt@5.0.0 added 68 packages from 100 contributors and audited 68 packages in 8.563s

But when I'm trying to see the bcrypt version in my terminal I have an error: $ bcrypt --version bash: bcrypt: command not found

and when I'm running my app I can't use bcrypt. Could you give me advice, please?

created time in 14 days

startedkelektiv/node-cron

started time in 14 days

startedkelektiv/node-cron

started time in 14 days

startedkelektiv/node.bcrypt.js

started time in 14 days

startedkelektiv/node.bcrypt.js

started time in 15 days

issue openedkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations.

Time Zone: "" - Cron String: 0 0 6,12,18 * * * - UTC offset: +05:30 - current Date: Tue Sep 08 2020 06:00:15 GMT+0530

at CronTime._getNextDateFrom (/root/repos/shopnow-micro-service/node_modules/cron/lib/cron.js:235:12) at CronTime.sendAt (/root/repos/shopnow-micro-service/node_modules/cron/lib/cron.js:156:17) at CronTime.getTimeout (/root/repos/shopnow-micro-service/node_modules/cron/lib/cron.js:175:29) at CronJob.start (/root/repos/shopnow-micro-service/node_modules/cron/lib/cron.js:613:31) at Timeout.callbackWrapper [as _onTimeout] (/root/repos/shopnow-micro-service/node_modules/cron/lib/cron.js:665:29) at ontimeout (timers.js:436:11) at tryOnTimeout (timers.js:300:5) at listOnTimeout (timers.js:263:5) at Timer.processTimers (timers.js:223:10)

created time in 15 days

startedkelektiv/node-cron

started time in 15 days

issue openedkelektiv/node.bcrypt.js

Application is interrupted without to say anything (NodeJs 12.13.1)

Node Version: 12.13.1

I'm using docker:

FROM node:11-alpine

WORKDIR /management-internal-admin

COPY package.json .
COPY package-lock.json .

RUN npm install --quiet

COPY . . 

EXPOSE 9000

CMD ["npm", "start:dev"]

When I'm trying to execute this code:

       try {
            const saltValue = await genSalt(10);
            const password = await hash(createUserDto.password, saltValue);
        } catch (error) {
            console.log(error);
        }

The container is exited without saying nothing.

Log:

m-i-admin                    | [Nest] 28   - 09/09/2020, 6:27:20 AM   [NestApplication] Nest application successfully started +7ms
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.517+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"connection accepted","attr":{"remote":"172.21.0.4:59214","sessionId":65,"connectionCount":6}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.518+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn65","msg":"client metadata","attr":{"remote":"172.21.0.4:59214","client":"conn65","doc":{"driver":{"name":"nodejs|Mongoose","version":"3.6.1"},"os":{"type":"Linux","name":"linux","architecture":"x64","version":"4.15.0-112-generic"},"platform":"'Node.js v11.15.0, LE (unified)","version":"3.6.1|5.10.3"}}}
m-i-admin                    | { useNewUrlParser: true,
m-i-admin                    |   useUnifiedTopology: true,
m-i-admin                    |   useCreateIndex: true }
m-i-admin                    | mongodb://root:root@mongo:27017/development-db-pitang?authSource=admin
m-i-admin                    | mongodb://root:root@mongo:27017/development-db-pitang?authSource=admin
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.682+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"connection accepted","attr":{"remote":"172.21.0.4:59220","sessionId":66,"connectionCount":7}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.683+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn66","msg":"client metadata","attr":{"remote":"172.21.0.4:59220","client":"conn66","doc":{"driver":{"name":"nodejs|Mongoose","version":"3.6.1"},"os":{"type":"Linux","name":"linux","architecture":"x64","version":"4.15.0-112-generic"},"platform":"'Node.js v11.15.0, LE (unified)","version":"3.6.1|5.10.3"}}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.684+00:00"},"s":"I",  "c":"NETWORK",  "id":22943,   "ctx":"listener","msg":"connection accepted","attr":{"remote":"172.21.0.4:59222","sessionId":67,"connectionCount":8}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.686+00:00"},"s":"I",  "c":"NETWORK",  "id":51800,   "ctx":"conn67","msg":"client metadata","attr":{"remote":"172.21.0.4:59222","client":"conn67","doc":{"driver":{"name":"nodejs|Mongoose","version":"3.6.1"},"os":{"type":"Linux","name":"linux","architecture":"x64","version":"4.15.0-112-generic"},"platform":"'Node.js v11.15.0, LE (unified)","version":"3.6.1|5.10.3"}}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.687+00:00"},"s":"I",  "c":"ACCESS",   "id":20250,   "ctx":"conn67","msg":"Successful authentication","attr":{"mechanism":"SCRAM-SHA-256","principalName":"root","authenticationDatabase":"admin","client":"172.21.0.4:59222"}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.849+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn66","msg":"connection ended","attr":{"remote":"172.21.0.4:59220","connectionCount":7}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.849+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn65","msg":"connection ended","attr":{"remote":"172.21.0.4:59214","connectionCount":5}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.850+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn64","msg":"connection ended","attr":{"remote":"172.21.0.4:59212","connectionCount":4}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.849+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn67","msg":"connection ended","attr":{"remote":"172.21.0.4:59222","connectionCount":6}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.850+00:00"},"s":"I",  "c":"-",        "id":20883,   "ctx":"conn63","msg":"Interrupted operation as its client disconnected","attr":{"opId":25930}}
mongo_1                      | {"t":{"$date":"2020-09-09T06:27:30.850+00:00"},"s":"I",  "c":"NETWORK",  "id":22944,   "ctx":"conn63","msg":"connection ended","attr":{"remote":"172.21.0.4:59210","connectionCount":3}}
m-i-admin exited with code 0

created time in 16 days

issue openedkelektiv/node-cron

Error: Something went wrong. cron reached maximum iterations.

Hello i got this error:

Time Zone: "" - Cron String: 0 0,30 8,9,10,11,12,13,14,15,16,17,18,19,20 * * * - UTC offset: +03:00 - current Date: Tue Sep 08 2020 17:00:09 GMT+0300

created time in 16 days

startedkelektiv/node-cron

started time in 16 days

startedkelektiv/node.bcrypt.js

started time in 16 days

startedkelektiv/node-cron

started time in 17 days

issue commentkelektiv/node.bcrypt.js

Does node12.18.3 not support the installation of bcrypt3.0.8?

@fengyh13 3.0.8 is no longer maintained, please upgrade to bcrypt 5. 3.0.8 also has security issues.

fengyh13

comment created time in 17 days

startedkelektiv/node-cron

started time in 17 days

startedkelektiv/node.bcrypt.js

started time in 17 days

issue openedkelektiv/node-cron

Stopping a cron after one-time execution

If I set a job to run once, do I need to do any cleanup? Like, do I need to call job.stop() at any point?

Here's my job:


  const date = new Date()

  date.setMinutes(date.getMinutes() + 5)

  const job = new CronJob(date, function () {
      // do stuff here
  })

  job.start()```

The job will run 5 minutes from now, which is what I want. Just curious if I NEED to call `job.stop()` at some point in the future

created time in 17 days

startedkelektiv/node-cron

started time in 17 days

issue openedkelektiv/node.bcrypt.js

Does node12.18.3 not support the installation of bcrypt3.0.8?

ubuntu 16.04.6 node 12.8.3 bcrypt 3.0.8

install bcrypt 3.0.8 error happened

created time in 17 days

more