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

Closed (moved)
Open
Opened Nov 18, 2018 by starlight@starlight

SBWS publishing badly broken vote documents

SBWS running as the longclaw bandwidth scanner began publishing vote documents with about 1600 descriptors on Saturday 11/17/18 at 15:00 UTC. Initially 1493 relay measurments were uploaded as reported here

https://lists.torproject.org/pipermail/tor-consensus-health/2018-November/009377.html

NOTICE: Bandwidth authorities have a substantially different number of measured entries: maatuska (6967), longclaw (1493), bastet (7042), gabelmoo (6949), moria1 (7084), Faravahar (7007)

the number of measurements declined each hour down to 1106 when this ticket was created during the hour following 11/18/18 05:00 UTC

the measurements uploaded appear to be stale values from several days ago, the last time SBWS was publishing from longclaw

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