Could not parse the date format about fusion HOT 4 OPEN

Just came back to this issue and I have to tell ... I have no clue what do to with this 😅

from fusion.

Maybe allow the user to configure an alternative fallback date format? Or try the CultureInfos for the cultures in
HKCU\Control Panel\International\User Profile\Languages
per process, until one of them fits?

Or assume that all dates are for the same day, or even just for today, if you can't parse them. This is likely to cover 99% of the usages. I doubt that a lot of people let Fusion++ collect logs overnight.

I realize that this is a pain, but aborting is not a good solution...

Maybe this sheds some light on the issue:
https://stackoverflow.com/questions/62909619/powershell-uiculture-vs-windows-setting
Or at least it documents that PowerShell's behavior is, er, noteworthy...

It's strange that PowerShell seems to be able to influence the CultureInfo used for formatting the log entries. The script was called in a Visual Studio build step and I have no idea what it does. However, since you're already displaying the offending timestamp, the user could easily figure out the proper fallback format, which may not be the same for every run! Configuring one (or even a series of) date format(s) could allow to successfully treat those odd scenarios.

from fusion.

You can't surely tell if the cultures under HKCU\Control Panel\International\User Profile\Languages would have done it in your case, do you?

from fusion.

Yes, they would have, but this may be a coincidence.

PowerShell's behavior is so confusing, and apparently even version-dependent.

from fusion.