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
Do we know if this is a PlaceCal issue or a TransDim one? I think we need to make sure the two projects tickets for this issue are properly separated out as it's a bit confusing to parse atm.
I think we decided this was a Trans Dim only issue. It's because Trans Dim explicitly uses timezone to make the dates from the ISO string and PlaceCal just uses the ISO string. I think
I think we decided this was a Trans Dim only issue. It's because Trans Dim explicitly uses timezone to make the dates from the ISO string and PlaceCal just uses the ISO string. I think
to narrow it down i think we should be comparing what's coming in through the graphql endpoint to whats displayed on the trans dimension - the other ticket needs updating to to only show the bug as it appears on placecal + the endpoint
kimadactyl
added
eee
Enormous Extra Effort (I have no idea how or needs breaking down)
vvv
Very Very Valuable
labels
Dec 8, 2024
Description
Events in The Trans Dimension calculate their time by converting ISO8601 string to UTC this is incorrect for some of the year
See https://www.gov.uk/when-do-the-clocks-change for ref on how to figure out whether we are in summertime
The text was updated successfully, but these errors were encountered: