Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
C
Collector
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 22
    • Issues 22
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Create a new issue
  • 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
  • Metrics
  • Collector
  • Issues
  • #33061

Closed
Open
Opened Jan 26, 2020 by starlight@starlight

archived bandwidth scanner files lack explicit source attibution

Current files in

https://collector.torproject.org/archive/relay-descriptors/bandwidths/ https://collector.torproject.org/recent/relay-descriptors/bandwidths/

lack indication of which bandwidth scanner generated them. (files archived from Tom's collection are attributed)

Collect these files here and abandoned an attempt to fill a gap due to this issue. Ad-hoc logic to bin them may be possible but is not trivial. Can provide attribution by sha256 digest for most of them if the file naming is improved.

original ticket legacy/trac#21378 (moved)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tpo/metrics/collector#33061