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
  • 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.

  • Legacy
  • TracTrac
  • Issues
  • #13084

Closed (moved)
Open
Opened Sep 08, 2014 by Roger Dingledine@arma

globe gets read/written backwards in its bandwidth graphs

https://atlas.torproject.org/#details/7552CA84FB125059DC2959A6BE01A6A8107B3523 shows a big jump in bandwidth, especially read bytes.

whereas https://globe.torproject.org/#/relay/7552CA84FB125059DC2959A6BE01A6A8107B3523 shows a big jump in bandwidth, but especially written bytes.

Examination of the extrainfo descriptor for the relay in question shows that it's read-history, not write-history, that has the big numbers.

So I think globe has its labels mixed up?

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: legacy/trac#13084