You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When PC time is set to "(UTC+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius", new Date(4331480400000) and moment(4331480400000).tz('Europe/Helsinki') returns different results.
MomentJs returns 120 offset, but it should be 180.
Issue starts to appear starting from 2038 year.
Expected result moment(4331480400000).tz('Europe/Helsinki').date() returns the same result as new Date(4331480400000) .getDate() .
The text was updated successfully, but these errors were encountered:
Windows is assuming today's time zone rule will repeat year over year indefinitely.
Moment-timezone has to project transitions at specific times, for each and every year. We can't go on forever, or our data size would be prohibitively large. We currently stop just before year 2038. Past that, we have no transition data.
Note that projecting transitions for any date in the future is making the assumption that nothing will change between now and then. The further out you go, the less likely this assumption is to be accurate. Even 2038 is a stretch, but we have to pick something.
When PC time is set to "(UTC+02:00) Helsinki, Kyiv, Riga, Sofia, Tallinn, Vilnius", new Date(4331480400000) and moment(4331480400000).tz('Europe/Helsinki') returns different results.
MomentJs returns 120 offset, but it should be 180.
Issue starts to appear starting from 2038 year.
Expected result moment(4331480400000).tz('Europe/Helsinki').date() returns the same result as new Date(4331480400000) .getDate() .
The text was updated successfully, but these errors were encountered: