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
{{ message }}
This repository has been archived by the owner on Jul 21, 2019. It is now read-only.
CFP would remain open through end of day local time (in the absence of a hour/minute setting which we don't yet have). Not actually expected - just incorrectly assumed.
Actual behavior
After midnight UTC, CFP appears closed on deployed site even though end of day isn't yet reached in the local TZ. Note that Minneapolis is missing on the deployed site but still appears locally. Conclusion: datetime is sadness.
Reproduction Steps
Set a CFP date to closing on a given day, and check after UTC-midnight.
The text was updated successfully, but these errors were encountered:
Truth be told, as annoying as it is, having the time will actually help us a bit with some additional features (regarding knowing exactly when something ends, like CFP's, etc)
Plus I have a sneaking suspicion this will solve our occasional event ordering problem.
Expected behavior
CFP would remain open through end of day local time (in the absence of a hour/minute setting which we don't yet have). Not actually expected - just incorrectly assumed.
Actual behavior
After midnight UTC, CFP appears closed on deployed site even though end of day isn't yet reached in the local TZ. Note that Minneapolis is missing on the deployed site but still appears locally. Conclusion: datetime is sadness.
Reproduction Steps
Set a CFP date to closing on a given day, and check after UTC-midnight.
The text was updated successfully, but these errors were encountered: