-
-
Notifications
You must be signed in to change notification settings - Fork 33.5k
Closed
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.
Description
There is a timezone bug in Node 10.16.0. It is the same bug that I reported to Chromium here:
https://bugs.chromium.org/p/chromium/issues/detail?id=928068
Run the code in comment 1, from there, to reproduce the bug in Node 10.16.0.
I'm not sure if this is a V8 thing or if each environment has to fix the bug. If it is a V8 thing, perhaps this bug will go away by itself eventually. Otherwise, it needs to be addressed in Node.
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.