microsoft
`<chrono>`: `time_zone::get_info` fails when the current code page cannot represent the localized time zone short ID.
See:
- Issue #3097
- PR #3102
- PR #3122
It seems likely that the result we want is for, if the abbreviation fails to convert, to instead attempt to format UTC+{} or UTC-{}.
If you are still there, the problem is still present. Has any thing changed during recent builds?
I don't believe so; we need someone who has time to do this, to actually do the work involved; unfortunately, none of the members of the team have had the time.
I have this piece of code:
const std::chrono::seconds::rep utcSeconds{ std::chrono::duration_cast<std::chrono::seconds>(std::chrono::utc_clock::now().time_since_epoch()).count() };
and it throws the exceptions saying The operation completed successfully. The exception is thrown on Windows Server 2012 R2 Datacenter. It works on Windows 11 Pro 22H2. When I use system_clock instead of utc_clock then the code works on the server edition, but when I compare the utc_clock and system_clock result on Windows 11 there is a 26s difference. Is this somehow relevant or should I open new issue?
