[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #28565 [Core Tor/sbws]: Report excluded results in a relay's bandwidth line
#28565: Report excluded results in a relay's bandwidth line
-------------------------------------------------+-------------------------
Reporter: teor | Owner: juga
Type: defect | Status:
| assigned
Priority: Medium | Milestone: sbws:
| 1.1.x-final
Component: Core Tor/sbws | Version:
Severity: Normal | Resolution:
Keywords: tor-bwauth, sbws-1.0-must- | Actual Points:
moved-20181128 |
Parent ID: #28547 | Points: 1
Reviewer: | Sponsor:
-------------------------------------------------+-------------------------
Comment (by juga):
Following the proposed KeyValues in https://pad.riseup.net/p/sbws-exclude-
reasons-keep:
- any KeyValue that is based on the last bandwidth file adds more code
complexity, because it would mean to read and parse the last bandwidth
file
- i created 4 additional header KeyValues to report the reasons why the
relays were exclued, that would make the KeyValue
`recent_measurement_exclusion_count` unneded, since it can be deduced from
the previous.
By the initial headers obtained in the Tor network is already explained
(or mostly) that sbws is reporting ~1000 relays less than torflow.
Branch: https://github.com/juga0/sbws/tree/ticket28565
Not creating PR, not changing to merge_ready since master is not in 1.1.X
version yet.
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/28565#comment:6>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs