[tor-bugs] #13084 [Globe]: globe gets read/written backwards in its bandwidth graphs

[Tor Bug Tracker & Wiki]

#13084: globe gets read/written backwards in its bandwidth graphs
------------------------+-----------------------------------------
     Reporter:  arma    |      Owner:  isis
         Type:  defect  |     Status:  assigned
     Priority:  normal  |  Milestone:
    Component:  Globe   |    Version:
   Resolution:          |   Keywords:  globe-0.4.10, ui, usability
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------------------------------
Changes (by isis):

 * keywords:   => globe-0.4.10, ui, usability
 * cc: isis (added)


Comment:

 Replying to [ticket:13084 arma]:
 >
 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?

 Nice catch. The `'written bytes per second'` and `'read bytes per second'`
 labels when mousing over the bandwidth graphs are indeed mixed up:

 {{{
 GLOBE.RelayBandwidthView = GLOBE.HistoryGraphView.extend({
     graphOpts: {
         labelsKMG2: true
     },
     title: 'Bandwidth',
     graphs: ['readHistory', 'writeHistory'],
     labels: ['written bytes per second', 'read bytes per second'],
     legendPos: [{x:60,y:25}, {x:270,y:25}]
 });
 }}}

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13084#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online