Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #33896

Closed (moved)
Open
Opened Apr 13, 2020 by Roger Dingledine@arma

Depictor: stop claiming so many digits of precision for clock skew

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

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#33896