Opened at 2016-07-05T23:37:10Z
Last modified at 2021-03-30T18:40:19Z
#2797 new defect
explain two timestamps on WUI server listings
| Reported by: | warner | Owned by: | |
|---|---|---|---|
| Priority: | minor | Milestone: | soon |
| Component: | code-frontend-web | Version: | 1.11.0 |
| Keywords: | wui easy | Cc: | |
| Launchpad Bug: |
Description
I loaded the current "welcome page", and the server columns have two separate (relative) timestamps.
The first is in the "Nickname" column, where it shows server nickname, long-form server ID (v0-base32stuff), a green/red checkmark/X connected-status indicator, and this timestamp.
The second is in the "Last RX" column.
I think the tooltips (which currently just show the corresponding absolute UTC timestamps) should also have a few words about what the timestamp is referring to. Based on the methods being called, I *think* the first one indicates the last time we established a connection to the server, and the second indicates the last time we've heard anything from that server, but I might be wrong.
For reference, the first timestamp is using IServer.get_last_connect_time(), and the second is using IServer.get_last_received_data_time().
Change History (3)
comment:1 Changed at 2016-07-05T23:39:37Z by warner
comment:2 Changed at 2020-06-30T14:45:46Z by exarkun
- Milestone changed from 1.13.0 to 1.15.0
Moving tickets out of closed milestones.
comment:3 Changed at 2021-03-30T18:40:19Z by meejah
- Milestone changed from 1.15.0 to soon
Ticket retargeted after milestone closed
Oh, and in the process, we should add those two methods to IServer (in src/allmydata/interfaces.py), since they aren't actually defined there yet. Those interface methods would be an ideal place to explain what these functions do (although I'll admit the method names are pretty good explanations all by themselves).