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

Closed (moved)
Open
Opened Apr 22, 2019 by teor@teor

Add data_period to the bandwidth file headers

atagar writes:

quick question about the new bandwidth file 1.4.0 headers: shouldn't data_period be in the header information? The spec defines it as "last data_period days. (data_period is 5 by default.)" but unless I'm missing something there's no way for the bandwidth file reader to know if data_period is the default or something else (and by extension what time period all these stats are over).

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