#28566: Report relays that sbws sees in the consensus, but never chooses to test -------------------------------------------------+------------------------- 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: -------------------------------------------------+------------------------- Changes (by juga):
* cc: pastly, juga (removed) * owner: (none) => juga * points: => 1 * status: new => assigned Comment: 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 - fetch consensus every hour (instead of every 5min) so that we can assume every consensus fetched is new - store the number of times a relay is in the consensus - created a KeyValue to report the number of time a reported relay was in the consensus - a header KeyValue with the total number of consensus could be calculated as the the maximum number of consensuses in a bandwidth line (maybe missing some?) - it can't be know the relays that were not in any consensus, since they won't be reported - it'd be possible to report the number relays that were not in any consensus Branch: https://github.com/juga0/sbws/tree/ticket28566 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/28566#comment:9> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online
_______________________________________________ tor-bugs mailing list tor-bugs@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs