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 2
    • Merge Requests 2
  • 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
  • #40071

Closed
Open
Created Mar 03, 2021 by juga @jugaMaintainer

Add KeyValue with the name of the dirauth

We've mentioned this several times, when searching for bugs: it would be easier to find out from which bwauth an archived Bandwidth File has been generated if it would be included in the file itself.

Currently it's only possible to correlate the hash of the file with the dirauth in the vote. Or guess it by the size of the file and the time it has been published, but it's just a guess.

This has also be commented in /tpo/metrics/collector#33061.

It also have more sense than having an scanner nickname.

Assignee
Assign to
sbws: 2.0.x-final
Milestone
sbws: 2.0.x-final
Assign milestone
Time tracking
None
Due date
None