tahoe-lafs/trac-2024-07-25

explain two timestamps on WUI server listings #2797

New issue

Open

opened 2016-07-05 23:37:10 +00:00 by warner · 3 comments

warner commented

2016-07-05 23:37:10 +00:00

Owner

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().

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()`.

tahoe-lafs added the

labels 2016-07-05 23:37:10 +00:00

tahoe-lafs added this to the 1.13.0 milestone 2016-07-05 23:37:10 +00:00

warner commented

2016-07-05 23:39:37 +00:00

Author

Owner

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).

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).

exarkun commented

2020-06-30 14:45:46 +00:00

Author

Owner

Moving tickets out of closed milestones.

tahoe-lafs modified the milestone from 1.13.0 to 1.15.0

2020-06-30 14:45:46 +00:00

meejah commented

2021-03-30 18:40:19 +00:00

Author

Owner

Ticket retargeted after milestone closed