Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TimeZone Europe/Rome Not Working #115

Closed
japita-se opened this issue Oct 9, 2018 · 10 comments
Closed

TimeZone Europe/Rome Not Working #115

japita-se opened this issue Oct 9, 2018 · 10 comments

Comments

@japita-se
Copy link

I am trying the nodecron in Italy and I set the timezone to Europe/Rome.
No cron strings are working.
If I do not set the timeone, everything is fine.
Why?

@merencia
Copy link
Member

merencia commented Oct 9, 2018

Hello @japita-se

It may be a bug, may you send me an example? And how are your current timezone?

@japita-se
Copy link
Author

My current timezone is Europe/Rome.
The example is very basic:
cron.schedule ("*/1 12 * * Monday-Sunday", () => console.log("Ehi!"), {timezone:'Europe/Rome'})

@merencia
Copy link
Member

Hey, I'm wondering about this issue, are you in daylight saving time?

@felixheck
Copy link

felixheck commented Oct 11, 2018

Got the same bug for Europe/Berlin — it triggers one hour before the scheduled time because it's using CET instead of CEST.

I switched to another module for now.

@merencia
Copy link
Member

@felixheck thanks for getting in touch.
Node-cron will support DST soon, I've created this issue #111 to do that.

@felixheck
Copy link

@merencia drop a line asa it’s available 😉 node-cron has a much better documentation and a better syntax imho. But without DST it’s currently kinda useless for me.

Keep me updated.
Thanks!

@alanclarke
Copy link

@merencia America/Vancouver is also missing

@alanclarke
Copy link

Unfortunately it doesn't seem possible to catch and handle this edge case, because it happens in a setTimeout

@benjamin21st
Copy link

benjamin21st commented Oct 21, 2019

America/New_York doesn't seem to work either.
Screen Shot 2019-10-21 at 1 57 37 PM

The second task doesn't return anything when clock hits 13:53 in New York

@merencia
Copy link
Member

moving to moment-timezone #248

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants