-
Notifications
You must be signed in to change notification settings - Fork 30.5k
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.UTC change in precision #56762
Comments
It looks like it changed specifically in 20.18.1 and 22.10.0. Possibly because of #55056 (I did not verify). EDIT: I tested on |
Interesting. FWIW, I don't get that result on a Mac (Darwin arm64) with either
|
Cross posting in case it is relevant: @targos mentioned in #56796 (comment) that the build infra updated from macOS 11 to macOS 13 around this time. |
Version
v22.13.1
Platform
Subsystem
No response
What steps will reproduce the bug?
From v20 on, there is a change in the output from the following command:
Versions less than v20 produce the following result:
Comparisons
How often does it reproduce? Is there a required condition?
All versions from v20 on produce a result that is different from previous versions as well as other JavaScript runtimes, including Chrome, Safari, Deno, and Bun.
What is the expected behavior? Why is that the expected behavior?
Unless this result is expected due to increased precision that should be documented, the expected behavior is to produce the same result consistent with Node.js versions before v20 and other JavaScript runtimes, including Chrome, Safari, Deno, and Bun.
What do you see instead?
34448384
instead of expected34447360
.Additional information
No response
The text was updated successfully, but these errors were encountered: