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
The date on the AMS production server defaults to UTC, and we don't change it when building stacks.
That date is used for ActiveRecord timestamp fields automatically, e.g. Push models.
The result is that UTC date/times are being stored in the DB.
We are not adjusting the date time for display, so displayed times are UTC (but there's no indicator).
To reproduce
Navigate to a Push (/pushes/[id]) where you already know about when it was created.
Note that the displayed date/time is UTC, and not a local time.
Background
I think storing the automatic ActiveRecord timestamps in UTC is a good idea, as it's agnostic of timezone.
Converting to the correct timezone should be the priority.
Defaulting to EST/EDT is fine for now, but...
Ideally we should first try to get the users actual timezone, then default to EST/EDT. If that's not hard, go for it in this ticket. Otherwise, just add the default EST/EDT conversion.
Done when
Date/time for Pushes should at default to EST (or EDT if we are in daylight time).
The text was updated successfully, but these errors were encountered:
The bug
To reproduce
/pushes/[id]
) where you already know about when it was created.Background
Done when
Date/time for Pushes should at default to EST (or EDT if we are in daylight time).
The text was updated successfully, but these errors were encountered: