Uh-oh! Thank you for spotting this! We'll look int...
# general
b
Uh-oh! Thank you for spotting this! We'll look into this!
f
πŸ‘
b
May I ask you what timezone you're in? Just to get full info πŸ™‚
f
I'm GMT-5
b
Awesome, thank you!
f
It was nothing.
b
@flat-article-86750 I'm trying to reproduce the error, but unfortunately I'm not able to. Is it possible to share the ID of this run? It's a uuid in the URL
projects/project_id/runs/run_id
. If yes, please send in my DM and I'll look up exactly what value causes the issue.
b
I suspect this is an
hourCycle
locale problem (AlΓ©xis and Vadim probably using different locales), possibly a Firefox issue, and reasonably easy to fix; https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Locale/hourCycle
b
Hey Duncan! πŸ™‚ Yes, apparently our Intl.DateTimeFormatOptions
hour12: false
is causing this problem even when we enforce
en-US
locale. According to this SO answer, Chrome thinks of this setting as
h24
, the fix would be simple - replace it with
hourCycle: 'h23'
. Thank you gentlemen, we will fix that! πŸ™‚ https://stackoverflow.com/a/60898146/142901
P.S. Time is hard πŸ˜„
@flat-article-86750 This issue should be fixed now! Thanks again for spotting it πŸ™‚
f
πŸ‘