loggerhead does not indicate the TZ of its timestamps

Bug #594591 reported by Jeroen T. Vermeulen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Launchpad itself
Fix Released
High
Robert Collins
loggerhead
Fix Released
High
Robert Collins

Bug Description

I'm trying to figure out what timezone the revision times in codebrowse are displayed in. For instance, I'm looking at revision 9467 on this page (currently the latest revision):

    https://code.edge.launchpad.net/~launchpad-pqm/launchpad/db-devel

This says "7 hours ago," which would be around 13:10 local or 06:10 UTC. Then I look at the detailed revision page:

    http://bazaar.launchpad.net/~launchpad-pqm/launchpad/db-devel/revision/9467?start_revid=9467

This pinpoints the revision at 06:54:01. That's clearly not my local time. If it were UTC it would be much closer to 6 hours ago. So... is it displaying British Summer Time?

Tags: qa-ok

Related branches

Revision history for this message
Stuart Bishop (stub) wrote :

This is RT #5513. All our servers run in BST, which confuses everyone outside of the UK.

I'd like to get our systems switched to UTC as part of the Lucid upgrade.

We can force individual components to run in UTC - I'm not sure which component this is though.

Revision history for this message
Robert Collins (lifeless) wrote :

Uhm, I'm totally sure this isn't an RT - it is a loggerhead bug, if you're referring to loggerhead pages, which you are.

Changed in loggerhead:
status: New → Confirmed
importance: Undecided → Medium
Revision history for this message
Robert Collins (lifeless) wrote :

The lp-code task can be closed when this is both fixed in loggerhead and deployed in production :).

For another sample - see http://bazaar.launchpad.net/~bzr-loom-devs/bzr-loom/trunk/revision/112 which claims 4am for me, but I did the commit around 3:30 PM.

I don't know if loggerhead has the users time preference, but it could at least show the TZ its using. I'd be inclined to show both:
time delta from now
time claimed in the commit in the commits timezone.

Revision history for this message
Stuart Bishop (stub) wrote :

The RT is about getting our servers running in UTC time. We don't want loggerhead displaying BST times as this confuses everyone outside of the UK. If Loggerhead is able to display commit times in the committer's timezone, or in the viewer's timezone, great. If not Loggerhead needs to convert local times to UTC times, or display local time and have local time set to UTC.

Revision history for this message
Robert Collins (lifeless) wrote : Re: [Bug 594591] Re: What timezone does codebrowse display?

Ack - the RT is a good thing to do, but it alone won't be enough to
fix the users confusion - we have to show *a* TZ :).

Aaron Bentley (abentley)
Changed in launchpad-code:
status: New → Triaged
importance: Undecided → Medium
Changed in loggerhead:
importance: Medium → High
status: Confirmed → Triaged
Changed in launchpad:
importance: Medium → High
summary: - What timezone does codebrowse display?
+ loggerhead does not indicate the TZ of its timestamps
tags: added: trivial
removed: lp-code
tags: removed: trivial
Changed in loggerhead:
assignee: nobody → Robert Collins (lifeless)
Changed in loggerhead:
status: Triaged → Fix Committed
Revision history for this message
Launchpad QA Bot (lpqabot) wrote :
tags: added: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Triaged → Fix Committed
assignee: nobody → Robert Collins (lifeless)
tags: added: qa-ok
removed: qa-needstesting
William Grant (wgrant)
Changed in launchpad:
status: Fix Committed → Fix Released
Changed in loggerhead:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.