Closed
Bug 194160
Opened 22 years ago
Closed 19 years ago
buglist.cgi has wrong time zone in datestamp at the top
Categories
(Bugzilla :: Query/Bug List, defect)
Tracking
()
RESOLVED
FIXED
Bugzilla 2.18
People
(Reporter: justdave, Assigned: Tomas.Kopal)
References
Details
Attachments
(1 file, 2 obsolete files)
661 bytes,
patch
|
bugreport
:
review+
|
Details | Diff | Splinter Review |
According to the editparams page, the timezone of the database server is supposed to be used anywhere there's a time. The timestamp at the top of the buglist.cgi page which tells when the query was run is shown in the local timezone of the webserver rather than the database server.
Reporter | ||
Comment 1•22 years ago
|
||
in the case where this was noticed, the webserver is in PST and the database server is in EST. :)
Comment 2•22 years ago
|
||
Doh. Is there a way to ask the SQL server what it's time is? Either that or we have compute all times in perl so they are based on the web servers time.
Reporter | ||
Comment 4•22 years ago
|
||
Reporter | ||
Updated•22 years ago
|
Target Milestone: --- → Bugzilla 2.18
Reporter | ||
Comment 5•22 years ago
|
||
Comment on attachment 114980 [details] [diff] [review] Patch v1 My only concern with this is we need to make sure that if the timezone param is empty that it still uses the local timezone...
Attachment #114980 -
Flags: review?(jake)
Comment 6•22 years ago
|
||
Comment on attachment 114980 [details] [diff] [review] Patch v1 That time is formated really funky... but I guess it always has been. If the Param() is empty, it instead uses UTC (and displays it as +0000). There is a special FILTER for time (the code is in Bugzilla::Util.pm), but it doesn't do any adjusting. Perhaps that should be made to use time2str? Using that filter would allow the time to be displayed in a more uniform manner.
Attachment #114980 -
Flags: review?(jake) → review-
Reporter | ||
Comment 7•22 years ago
|
||
Yeah, if it's using UTC without a timezone defined then it needs an IF loop for it... The ugly display is how it's always been. I'm just concerned with getting the correct timezone on the existing output here. :)
Attachment #114980 -
Attachment is obsolete: true
Reporter | ||
Updated•22 years ago
|
Attachment #114982 -
Flags: review?(jake)
Comment 8•21 years ago
|
||
Dave, why not use Bugzilla::Util->format_time(), which prints out the time prettier *and* supports the timezone Param?
Status: NEW → ASSIGNED
Updated•20 years ago
|
Summary: buglist.cgi has wrong timezone in datestamp at the top → buglist.cgi has wrong time zone in datestamp at the top
Reporter | ||
Comment 9•20 years ago
|
||
Comment on attachment 114982 [details] [diff] [review] Patch v2 per kiko's comment 8
Attachment #114982 -
Flags: review?(jake) → review-
Reporter | ||
Comment 10•20 years ago
|
||
This should be a quick fix, but I don't have time to do it myself...
Assignee: justdave → nobody
Status: ASSIGNED → NEW
Reporter | ||
Updated•19 years ago
|
Flags: blocking2.20+
Flags: blocking2.18.1+
Reporter | ||
Comment 11•19 years ago
|
||
*** Bug 285430 has been marked as a duplicate of this bug. ***
Assignee | ||
Updated•19 years ago
|
Assignee: nobody → Tomas.Kopal
Assignee | ||
Updated•19 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 12•19 years ago
|
||
Actually, original text was "Thu Mar 17 16:36:36 +63000 2005", format_time prints it as "2005-03-17 16:36". I think the original looks better. Which means Dave's patch is ok :-). Comments?
Assignee | ||
Comment 13•19 years ago
|
||
When the timezone is not defined, we should not print it. I have also moved the year to be next to date, not time.
Attachment #114982 -
Attachment is obsolete: true
Attachment #177712 -
Flags: review?
Updated•19 years ago
|
Attachment #177712 -
Flags: review? → review+
Updated•19 years ago
|
Flags: approval?
Flags: approval2.18?
Updated•19 years ago
|
Whiteboard: patch awaiting approval
Reporter | ||
Updated•19 years ago
|
Flags: approval?
Flags: approval2.18?
Flags: approval2.18+
Flags: approval+
Reporter | ||
Comment 14•19 years ago
|
||
Actually, I take that back. Why aren't we using format_time()? Does it do something wrong? The date display on show_bug has a timezone, how do we do it there?
Flags: approval2.18+
Flags: approval+
Assignee | ||
Comment 15•19 years ago
|
||
(In reply to comment #14) > Actually, I take that back. Why aren't we using format_time()? Does it do > something wrong? The date display on show_bug has a timezone, how do we do it > there? Format_time is meant to be used with times from the DB, not perl times. We can't use it without major hurdle. Probably better way would be to switch this time to use DB time instead of perl time(), and to have all the times use the same source (e.g. if DB and web server are different machines, the time and timezone can be different). Trouble is that we are using perl time all over the code (e.g. report.cgi - perl time, again custom formatting, no timezone), so that would be a major rework. We should do it, but probably not now, in freeze.
Reporter | ||
Comment 16•19 years ago
|
||
OK, let's do this. I think we have another bug somewhere for consolidating perl vs DB time in the code. Should find that bug and add a reminder there to fix this when we do that.
Flags: approval2.18+
Flags: approval+
Comment 17•19 years ago
|
||
Tip: Checking in template/en/default/list/list.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/list/list.html.tmpl,v <-- list.html.tmpl new revision: 1.36; previous revision: 1.35 done 2.18: Checking in template/en/default/list/list.html.tmpl; /cvsroot/mozilla/webtools/bugzilla/template/en/default/list/list.html.tmpl,v <- - list.html.tmpl new revision: 1.25.2.2; previous revision: 1.25.2.1 done
Status: ASSIGNED → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
Whiteboard: patch awaiting approval
Comment 18•19 years ago
|
||
Do we know the bug number for this time consolodation by chance? Part of the reason that format_time exists is so all our times can be consistant. This is also very helpful for (and should be a prereq for) bug 182238.
Assignee | ||
Comment 19•19 years ago
|
||
(In reply to comment #18) > Do we know the bug number for this time consolodation by chance? Part of the > reason that format_time exists is so all our times can be consistant. This is > also very helpful for (and should be a prereq for) bug 182238. I think bug 283076 is the closest to this, although it has drifted a bit during the discussion.
Comment 20•19 years ago
|
||
Not sure why this is marked as fixed. Bugzilla 2.18.1 has patch "V3" in it, but all that does is print the UTC time followed by the configured timezone, which is even more confusing.
Comment 21•17 years ago
|
||
(In reply to comment #20) > Not sure why this is marked as fixed. Bugzilla 2.18.1 has patch "V3" in it, > but all that does is print the UTC time followed by the configured timezone, > which is even more confusing. That means that your server is set to UTC time. Bugzilla does not do timezone translation. If it's doing timezone translation anywhere, that's a bug, at the moment.
Comment 22•17 years ago
|
||
(In reply to comment #21) > That means that your server is set to UTC time. No it isn't: # date Mon Jun 4 18:00:47 PDT 2007 # date -u Tue Jun 5 01:00:49 UTC 2007
Updated•12 years ago
|
QA Contact: matty_is_a_geek → default-qa
You need to log in
before you can comment on or make changes to this bug.
Description
•