-
-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
timezone issues with opened date #876
Comments
@owocki, @mbeacom seems like switching to UTC timezone solves problem. I agree that dates should be stored in UTC format.
What do You think about changing timezone ? Seems to be fundamental change and i'm not aware of all django internals and problems it might rise with current implementation. |
Time zone funkiness is why I changed my life to be running on UTC, just one less thing to worry about :)
|
@kziemianek Agreed. We should ensure we're storing UTC and implement: https://docs.djangoproject.com/en/2.0/topics/i18n/timezones/ |
@mbeacom what do you think about changing settings.py:163 to set the default as UTC as a means of solving the original issue? |
fixed in #919 (comment) |
thanks @kziemianek |
⚡️ A tip worth 0.025 ETH (12.85 USD @ $513.94/ETH) has been granted to @kziemianek for this issue from Kevin. ⚡️ The sender had the following public comments:
Nice work @kziemianek! To redeem your tip, login to Gitcoin at https://gitcoin.co/explorer and select 'Claim Tip' from dropdown menu in the top right, or check your email for a link to the tip redemption page.
|
http://bits.owocki.com/2I460x3e1T0Z/Screen%20Shot%202018-04-12%20at%202.30.06%20PM.png
https://gitcoin.co/issue/gitcoinco/web/865
This bounty was really opened 3 hours ago but the 'opened' date says 10 hours ago
The text was updated successfully, but these errors were encountered: