Sean Lynch (Inactive)
added a comment - 19/Nov/10 11:59 AM Resolving as duplicate since we have a story to upgrade Erlang anyway and having a separate bug to track the timezone issue just clutters Jira.

Perry Krug
added a comment - 07/Dec/10 6:50 PM I respectfully disagree. Having a separate bug for this issue means we can verify that it is actually fixed and make the necessary customer notifications if necessary.

unable to reproduce this on 1.7. beta builds
I changed the vm's time zone to Jakart (wit) which is said to be broken on couchdb jira project
I was able to login to the UI without any problem and could see the logs.

Farshid Ghods (Inactive)
added a comment - 23/May/11 6:01 PM unable to reproduce this on 1.7. beta builds
I changed the vm's time zone to Jakart (wit) which is said to be broken on couchdb jira project
I was able to login to the UI without any problem and could see the logs.
Tue May 24 06:00:34 WIT 2011