-
Notifications
You must be signed in to change notification settings - Fork 835
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
After 2030, time zone offset is wrong #803
Comments
Yep, bug, and it happens for many timezones for date > 2039. Will be fixed in upcoming releases. |
For reference, this has been happening since 0.5.26 — see #768 |
Yep, people (in moment-timezone team) releasing on a Mac (with 32 bit zdump) have range until 2047, and people releasing on Linux (with 64bit zdump) have range until 2437. If you use 0.5.37 (latest, with 2022c) it has "extended" range (and bigger file size, if you care). @Czytx can you please share what are you using these timestamps for so far in the future? I mean there is high likelyhood that goverments will change DST rules in the next 50 years, so it would still be wrong. tzdb is released multiple times a year (with corrections) for a reason. |
1.moment.tz("2020-04-10 04:00:00","Australia/Adelaide").format()
the result is : "2020-04-10T04:00:00+09:30"
2. moment.tz("2069-04-10 04:00:00","Australia/Adelaide").format()
the result is : "2069-04-10T04:00:00+10:30" , the timezone offset is +10:30 but it should be 09:30
The text was updated successfully, but these errors were encountered: