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

Closed (moved)
Open
Opened Mar 11, 2010 by Roger Dingledine@arma

Authority that doesn't make a consensus never fetches one from elsewhere

If moria1 fails to participate in making the consensus (e.g. it's down, or it doesn't support the consensus method that is chosen for the consensus), then it doesn't have a consensus for that period. It should realize it doesn't have the newest consensus, and try to fetch one from the other authorities.

This bug is especially relevant while we have authorities that don't like the consensus method in use -- currently dizum and dannenberg haven't upgraded, so they never sign the consensus, so any clients (or relays!) who ask them for a consensus have to retry elsewhere. I imagine the bug slows down bootstrapping too.

[Automatically added by flyspray2trac: Operating System: All]

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