#1972 closed enhancement (fixed)

wui: show time page was rendered

Reported by: leif Owned by: daira
Priority: normal Milestone: 1.10.1
Component: code-frontend-web Version: 1.10.0
Keywords: usability wui welcome time Cc:
Launchpad Bug:

Description

While troubleshooting something, I found myself with several open browser tabs showing my gateway in different states and realized that I did not know which view was rendered when.

It would be useful to include a timestamp at the bottom of the page (alongside the verbose version information already present).

Change History (11)

comment:1 Changed at 2013-05-19T06:32:14Z by leif

When there is at least one disconnected server, the page render time is currently displayed in the "since" column. (#1973)

comment:3 Changed at 2013-05-19T22:05:17Z by daira

  • Component changed from unknown to code-frontend-web
  • Keywords usability wui welcome time review-needed added
  • Milestone changed from undecided to 1.11.0
  • Owner changed from davidsarah to daira
  • Status changed from new to assigned

Reviewing.

comment:4 Changed at 2013-05-19T22:33:59Z by Daira Hopwood <david-sarah@…>

  • Resolution set to fixed
  • Status changed from assigned to closed

In ec191bfca6e1cd3d31b4f206c56304caa69c82cf/trunk:

WUI: add time page was rendered to client and introducer welcome pages. closes #1972

Author: Leif Ryge <leif@…>
Signed-off-by: Daira Hopwood <david-sarah@…>

comment:5 Changed at 2013-05-19T22:36:02Z by daira

  • Keywords review-needed removed

I added some tests and changed the time format to be consistent with the 'Announced' and 'Since' columns.

comment:6 Changed at 2013-05-22T23:43:00Z by zooko

Per #1077 timestamps should be generated by a call to time_format.py.

comment:7 follow-up: Changed at 2013-05-23T03:32:49Z by daira

iso_utc and iso_local in time_format.py output time to nanosecond resolution, which is false precision and not appropriate for this use. Also iso_local doesn't include an RFC 3339 timezone offset.

comment:8 in reply to: ↑ 7 ; follow-up: Changed at 2013-05-23T05:26:35Z by zooko

Replying to daira:

iso_utc and iso_local in time_format.py output time to nanosecond resolution, which is false precision and not appropriate for this use. Also iso_local doesn't include an RFC 3339 timezone offset.

How about making those issues separate tickets?

comment:9 in reply to: ↑ 8 Changed at 2013-05-25T01:07:31Z by daira

Replying to zooko:

Replying to daira:

iso_utc and iso_local in time_format.py output time to nanosecond resolution, which is false precision and not appropriate for this use. Also iso_local doesn't include an RFC 3339 timezone offset.

How about making those issues separate tickets?

Why would we change the timestamp to a more ugly format only so that we have to fix it again? Let's change iso_utc and iso_local first.

comment:10 follow-up: Changed at 2013-05-25T01:10:24Z by zooko

This ticket should be rewritten to: "Make all timestamps be generated by the same code, and be in a consistent format with one another.".

comment:11 in reply to: ↑ 10 Changed at 2013-05-25T01:11:03Z by zooko

Replying to zooko:

This ticket should be rewritten to: "Make all timestamps be generated by the same code, and be in a consistent format with one another.".

Sorry, I mean *that* ticket -- #1077.

Note: See TracTickets for help on using tickets.