Changes between Initial Version and Version 7 of Ticket #28355


Ignore:
Timestamp:
Nov 7, 2018, 2:35:15 PM (2 years ago)
Author:
teor
Comment:

i think torflow is just including more relays because it doesn't check the restrictions we added.

We have a policy that sbws should match torflow, unless we have a very good reason. (Like a bad bug in torflow.)

Adding the restrictions to sbws in #27338 has caused a major bug: it does not match torflow.

Here's what I think we've tried so far:

  • fixing the sbws scheduler
  • disabling rtt

Are these fixes in longclaw's version of sbws?

If we can't get the restrictions to work, we should disable them by default, so sbws matches torflow. Then we should open a ticket to review them in a later release.

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #28355

    • Property Status changed from assigned to needs_information
    • Property Component changed from Core Tor/DocTor to Core Tor/sbws
    • Property Summary changed from Do not notify about bwauths out of sync to Disable measurement timing rules on sbws by default
    • Property Milestone changed from to sbws 1.0 (MVP must)
    • Property Type changed from task to defect
  • Ticket #28355 – Description

    initial v7  
    11Currently sbws include less relays in its report, mostly due to https://trac.torproject.org/projects/tor/ticket/27338#comment:6.
    22
    3 While sbws is not changed to include more relays, maybe the notice message about
    4 "Bandwidth authorities have a substantially different number of measured entries" should not be sent.
     3~~While sbws is not changed to include more relays, maybe the notice message about
     4"Bandwidth authorities have a substantially different number of measured entries" should not be sent.~~
     5
     6sbws should disable these restrictions, so it matches torflow.