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
  • #4250

Closed (moved)
Open
Opened Oct 17, 2011 by Roger Dingledine@arma

metrics consensus health should check the consensus from each authority

While doing a training yesterday, my poor os x user started tbb and it fetched a consensus that had two signatures on it -- one from gabelmoo-legacy, and one from moria1-legacy.

I didn't catch which authority gave it to her.

Several minutes later, Tor tried another authority and bootstrapped from there.

While we're checking network health, we should fetch a consensus from each authority and see if it is recent enough and has enough signatures on it.

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