Labels: -Priority-Medium -Milestone-Release1.0 Priority-Low
Comment #4 on issue 1105 by chipx86: Time shown in dashboard does not match
I verified that new review requests do indeed get the correct timezone.
you'll need to restart your web server after setting this option due to how
Python processes handle timezone settings. The process setting the option
updated properly, but the other processes may not. We may be able to look
for 1.1 or 1.5, but for now, try restarting your server and seeing if that
things. It seems to work for other people.
For the record, old timestamps will not be updated for the new timezone
are stored in the database as actual written dates/times, and are not based
active timezone. This is beyond our control.
At the very least, we'll want to document this.
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
You received this message because you are subscribed to the Google Groups
To post to this group, send email to firstname.lastname@example.org
To unsubscribe from this group, send email to
For more options, visit this group at