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
Describe the bug
In old Windows versions, FILETIME didn't count leap seconds. Since Windows 10 1809, Windows has become aware of leap seconds, and FILETIME counts leap seconds after 2018-06 by default (could be turned off system-wide to restore the old behavior).
Currently, system_clock::now() assumes the old behavior that FILETIME doesn't count leap seconds (#1520):
Describe the bug
In old Windows versions,
FILETIME
didn't count leap seconds. Since Windows 10 1809, Windows has become aware of leap seconds, andFILETIME
counts leap seconds after 2018-06 by default (could be turned off system-wide to restore the old behavior).Currently,
system_clock::now()
assumes the old behavior thatFILETIME
doesn't count leap seconds (#1520):STL/stl/inc/chrono
Lines 666 to 668 in 4ee3f91
But
file_clock::from_utc()
andfile_clock::to_utc()
assume thatFILETIME
always counts leap seconds after 2017:STL/stl/inc/chrono
Lines 3324 to 3325 in 4ee3f91
We should fix all of them to return the correct result whether or not the system is leap second aware.
STL version
4ee3f91
The text was updated successfully, but these errors were encountered: