Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • S sbws
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #28158

Closed
Open
Created Oct 23, 2018 by juga@jugaMaintainer

Vote for relay bandwidths even if the min percentage has not been reached

In legacy/trac#28062 (moved) we add additional header lines when the minimum percentage of measured relays that pass some restrictions and do not write any bandwidth lines. A dirauth asked if that is better that writing the few bandwidth lines. The reason why we do it is because torflow does it and we want sbws 1.0 to behave as torflow. In future sbws versions, we might prefer to include the bandwidth lines

Assignee
Assign to
Time tracking