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

Closed (moved)
Open
Opened Mar 31, 2016 by teor@teor

Fallback Directory Selection should exclude down relays earlier

The updateFallbackDirs.py script uses OnionOO to find a list of candidate directory mirrors, then checks the consensus download speed from each mirror.

Previously, the script allowed relays that had a good uptime history, but just happened to be down right now.

But this doesn't work any more, because those relays can't provide a consensus, so we exclude them in the final consensus download check.

We could be smarter, and avoid the effort of that check by eliminating relays that aren't running right now from the list of fallback candidates.

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