[metrics-bugs] #33896 [Metrics/Consensus Health]: Depictor: stop claiming so many digits of precision for clock skew

[Tor Bug Tracker & Wiki]

#33896: Depictor: stop claiming so many digits of precision for clock skew
------------------------------------------+-----------------
     Reporter:  arma                      |      Owner:  tom
         Type:  defect                    |     Status:  new
     Priority:  Medium                    |  Milestone:
    Component:  Metrics/Consensus Health  |    Version:
     Severity:  Normal                    |   Keywords:
Actual Points:                            |  Parent ID:
       Points:                            |   Reviewer:
      Sponsor:                            |
------------------------------------------+-----------------
 In
 https://consensus-health.torproject.org/#authorityclocks
 we state clock skew numbers like "-0.386114 seconds".

 There's no way that 114 part is at all accurate, since this figure is
 influence by (for example) network latency, Tor processing latency, etc.

 We list only 1 or 2 or 3 digits after the decimal point. I'm thinking two
 digits would be a nice balance.

 Motivated by the discussion on tor-relays@:
 https://lists.torproject.org/pipermail/tor-relays/2020-April/018372.html

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/33896>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online