Opened 11 months ago

Last modified 2 months ago

#28509 new defect

Limit relay bandwidth self-tests based on RelayBandwidthRate, not BandwidthRate

Reported by: teor Owned by:
Priority: Medium Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-bwauth, 035-backport, 029-backport-maybe-not, 041-proposed, needs-proposal, 034-unreached-backport-maybe, 033-unreached-backport-maybe
Cc: Actual Points:
Parent ID: #22453 Points:
Reviewer: Sponsor:


Discovered while working on #22453.

This is a bug on, where RelayBandwidthRate was introduced.

Child Tickets

Change History (9)

comment:1 Changed 9 months ago by nickm

Keywords: 041-proposed added
Milestone: Tor: 0.4.0.x-finalTor: unspecified

comment:2 Changed 8 months ago by teor

These open, non-merge_ready tickets can not get backported to 0.3.3, because 0.3.3 is now unsupported.

comment:3 Changed 8 months ago by teor

Keywords: 033-backport-unreached added

Hmm, I guess they should still get 033-backport-unreached

comment:4 Changed 6 months ago by teor

Keywords: needs-proposal added

These tickets need a proposal before we write any code.

The two competing proposals in #22453 are:

  1. Remove the bandwidth self-test
  2. Increase the bandwidth self-test so it measures a reasonable amount of bandwidth

comment:5 Changed 4 months ago by nickm

Removing 034-backport from all open tickets: 034 has reached EOL.

comment:6 Changed 2 months ago by teor

Keywords: 034-unreached-backport-maybe added; 034-backport-maybe removed

0.3.4 is unsupported, we won't be backporting anything else to it.

comment:7 Changed 2 months ago by teor

Keywords: 033-unreached-backport added; 033-backport-unreached removed

Fix 033-unreached-backport spelling.

comment:8 Changed 2 months ago by teor

Keywords: 033-unreached-backport-maybe added; 033-backport-maybe removed

Remove outdated 033-backport-maybe

comment:9 Changed 2 months ago by teor

Keywords: 033-unreached-backport removed
Note: See TracTickets for help on using tickets.