Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
S
sbws
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 121
    • Issues 121
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 3
    • Merge Requests 3
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • 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.

  • The Tor Project
  • Network Health
  • sbws
  • Issues
  • #28158

Closed
Open
Opened Oct 23, 2018 by juga @juga💬Maintainer

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
sbws: 1.2.x-final
Milestone
sbws: 1.2.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/network-health/sbws#28158