Title
#general
Vadim (Infracost)

Vadim (Infracost)

08/15/2022, 4:37 PM
Uh-oh! Thank you for spotting this! We'll look into this!
a

Aléxis Mosquera Caicedo

08/15/2022, 4:38 PM
👍
Vadim (Infracost)

Vadim (Infracost)

08/15/2022, 4:38 PM
May I ask you what timezone you're in? Just to get full info 🙂
a

Aléxis Mosquera Caicedo

08/15/2022, 4:38 PM
I'm GMT-5
Vadim (Infracost)

Vadim (Infracost)

08/15/2022, 4:39 PM
Awesome, thank you!
a

Aléxis Mosquera Caicedo

08/15/2022, 4:39 PM
It was nothing.
Vadim (Infracost)

Vadim (Infracost)

08/15/2022, 5:20 PM
@Aléxis Mosquera Caicedo 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.
Duncan

Duncan

08/16/2022, 7:59 AM
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
Vadim (Infracost)

Vadim (Infracost)

08/16/2022, 9:52 AM
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
9:52 AM
P.S. Time is hard 😄
3:26 PM
@AlĂ©xis Mosquera Caicedo This issue should be fixed now! Thanks again for spotting it 🙂
a

Aléxis Mosquera Caicedo

08/16/2022, 11:50 PM
👍