-
Notifications
You must be signed in to change notification settings - Fork 30.3k
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
Date not updated after system timezone change #4022
Comments
Duplicate of #3449 |
@evanlucas I think this is different issue here, in that case timezone has changed from system level but nodejs not see this change. > new Date();
Wed Nov 25 2015 17:04:27 GMT+0100 (Central European Standard Time)
// changing timezone -> Date and Time -> change timezone..
> new Date();
Wed Nov 25 2015 17:04:38 GMT+0100 (Central European Standard Time) |
@sebmj does it apply after a reboot? What OS? |
Tested on WIndows 7, after nodejs restart timezone is correct, issue 2015-11-25 19:56 GMT+01:00 Jeremiah Senkpiel notifications@github.com:
|
The problem is that we don't really have a way to be notified that the timezone changed. You can manually reset the date cache via v8, but it is costly. (https://github.com/evanlucas/reset-date-cache) |
Nor is it necessarily desirable for the zone to suddenly change. |
Closing as there is not really anything actionable to do at this point. Thanks! |
@evanlucas agree |
When system timezone has changed during nodejs running new Date() is not updated with proper timezone and still works in old one. This is caused by V8 caching current date. Any suggestions how to solve this issue?
The text was updated successfully, but these errors were encountered: