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 119
    • Issues 119
    • 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
  • #30724

Closed
Open
Opened Jun 02, 2019 by teor@teor

Work out why relay_in_recent_consensus_count is 13 days for some relays

In longclaw's bandwidth file:

1559468088
version=1.4.0
earliest_bandwidth=2019-05-28T09:35:16
file_created=2019-06-02T09:35:04

One relay has:

master_key_ed25519=Q2Ft/AsNiru+HEx4KRdRxhnuohOs3ByA0t816gUG+Kk
nick=che node_id=$D5F2C65F4131A1468D5B67A8838A9B7ED8C049E2
relay_in_recent_consensus_count=310

310/24 = 12.9 days, but sbws is only supposed to count 5 recent days.

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#30724