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 Mar 8, 2021. It is now read-only.
If you work on notes for clinic in the afternoon/evening (specifically after 6pm, given that we're currently in CST), SNHC says "Good morning, it looks like you're the first one here", etc. and has the date for Sunday. This is consistent with the server time being in UTC, not CST (6:01pm on Saturday CST is 12:01am on Sunday UTC).
The text was updated successfully, but these errors were encountered:
Good catch. I thought we had this fixed. It's a bit more complicated than the server time vs the local time, because django is supposed to be time-zone aware. Typically, this type of problem crops up when python's datetime.datetime.now() is used instead of django.utils.timezone.now(), which is aware of the server's "local" timezone.
Presumably this error is in workup/views.py wherever the view that checks if there is a ClinicDate object for "today" is (and generates a new one if so).
If you work on notes for clinic in the afternoon/evening (specifically after 6pm, given that we're currently in CST), SNHC says "Good morning, it looks like you're the first one here", etc. and has the date for Sunday. This is consistent with the server time being in UTC, not CST (6:01pm on Saturday CST is 12:01am on Sunday UTC).
The text was updated successfully, but these errors were encountered: