deadlock

[fabiooshiro]

console.log('fist')
new CronJob('0 0 9 4 * *', (function() {
  console.log('message');
}), null, true, 'America/Sao_Paulo');
console.log('second')

output
first

[ncb000gt]

Are you seeing this if you take out the DoM specificity? What about if you remove the timezone?

Have you been able to pinpoint anything inside the library as the culprit?

[ncb000gt]

I'm able to reproduce this. Thanks.

[ncb000gt]

@fabiooshiro we looked into this (mostly @jodevsa) and found some strange behavior when adding 1d and then setting the hours/minutes/seconds to 0. It appears as though only 23 hours are being added going into the 4th of the month.

I pushed a change that should help with the deadlock until we can figure out the larger resolving solution. Let me know if this works. @jodevsa is going to link to a ticket he's going to create over in the moment-tz project.

[ncb000gt]

The tests appear to be failing, but not individually. I'll look into these later when I get a moment.

[Roger13]

I'm still having this issue. Do we have a fix?

[ncb000gt]

We should have commented here, sorry about that! We pushed a couple changes to fix the specific problem outlined above, and to update the tests. But, the fix we put in place was specifically for Sao_Paulo.

@Roger13 did you pull the latest from npm? can you double check the cron package.json in your node_modules directory? Also, are you using a timezone and if so, what is it? Any code you can share would be helpful too.

thanks!

[Roger13]

Trying to run the following snippet, also using Sao_Paulo timezone:

console.log('start')
const reportCron = new CronJob('0 0 0 5,15 * *', () => console.log('Running'), null, true, 'America/Sao_Paulo')
console.log('finish')

Output: start

@ncb000gt Just ran a npm update, still having the issue, currently running cron@1.4.1

[ncb000gt]

@Roger13 sorry, I edited the comment above. Can you share any more? Thanks!

[Roger13]

@ncb000gt I don't know if you saw the snipped I shared on the comment above. Any update?

[ncb000gt]

@Roger13 hey, turns out we didn't publish the code to npm, sorry about this, slight miscomm. I've published 1.5.0 to npm. Pull that down and try it again. Let me know if you're still seeing this issue. Sorry about this and thanks!