explain two timestamps on WUI server listings #2797
Labels
No Label
0.2.0
0.3.0
0.4.0
0.5.0
0.5.1
0.6.0
0.6.1
0.7.0
0.8.0
0.9.0
1.0.0
1.1.0
1.10.0
1.10.1
1.10.2
1.10a2
1.11.0
1.12.0
1.12.1
1.13.0
1.14.0
1.15.0
1.15.1
1.2.0
1.3.0
1.4.1
1.5.0
1.6.0
1.6.1
1.7.0
1.7.1
1.7β
1.8.0
1.8.1
1.8.2
1.8.3
1.8β
1.9.0
1.9.0-s3branch
1.9.0a1
1.9.0a2
1.9.0b1
1.9.1
1.9.2
1.9.2a1
LeastAuthority.com automation
blocker
cannot reproduce
cloud-branch
code
code-dirnodes
code-encoding
code-frontend
code-frontend-cli
code-frontend-ftp-sftp
code-frontend-magic-folder
code-frontend-web
code-mutable
code-network
code-nodeadmin
code-peerselection
code-storage
contrib
critical
defect
dev-infrastructure
documentation
duplicate
enhancement
fixed
invalid
major
minor
n/a
normal
operational
packaging
somebody else's problem
supercritical
task
trivial
unknown
was already fixed
website
wontfix
worksforme
No Milestone
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Reference: tahoe-lafs/trac-2024-07-25#2797
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
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 usingIServer.get_last_received_data_time()
.Oh, and in the process, we should add those two methods to
IServer
(insrc/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).Moving tickets out of closed milestones.
Ticket retargeted after milestone closed