-
-
Notifications
You must be signed in to change notification settings - Fork 52
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
Specifying timezone causes no trigger using croner <= 7.x #225
Comments
Interersting, can confirm this happens with multiple timezones resolving to AKDT. |
@jefbarn Please check if upgrading to |
Verified croner@7.0.6-dev.0 is working with timezone: 'America/Anchorage' |
Released in stable channel through |
Thanks for the fix @Hexagon . However I tried the 7.0.6-dev.0 branch with Node.js 16 and it throws the following error:
I'm guessing the syntax in 7.0.6-dev.0 is only supported for Node.js >= 18. We're unable to move to Node.js 18 at the moment due to hardware vendor limitation. Is there any chance you can make this bugfix work with Node.js 16? Thx again. |
@victorird Oh, thanks for reporting this! Released a potential hot fix in // Convert non-supported timezones
// - Hotfix for AKST and AKDT 7.0-branch of Croner, fixed for real in 8.0
tz = tz.replace("AKST","-0900").replace("AKDT","-0800"); Hacky, but i hope it should do for those who cannot go to |
Thanks for the quick hot fix. I tested it and it's working flawlessly! |
Nice! Added support for AST and released |
Resolved in the 7.x branch through |
This doesn't do anything:
This works:
The text was updated successfully, but these errors were encountered: