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 133
    • Issues 133
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 4
    • Merge Requests 4
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

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

Closed
Open
Opened Dec 21, 2020 by juga @jugaMaintainer

Stop trying to measure relays not in the consenus

When we implemented #30727 (closed), we started to measure relays that are not in the last consensus. I think this is the cause why there's still around ~450 relays (see #40029 (closed)) failing to be measured because of circuit errors. We didn't realize that what we needed to do is to include these relays in the bandwidth file (and we already do, maybe we should just keep more days #40017 (closed)), but not in the list of relays to measure. The patch is simple, i'd try it.

Assignee
Assign to
sbws: 1.1.x-final
Milestone
sbws: 1.1.x-final
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/network-health/sbws#40037