Opened 9 years ago

Last modified 8 months ago

#4269 new defect

Improve slice handling in bw auths

Reported by: mikeperry Owned by:
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords:
Cc: karsten, aagbsn, mikeperry Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


Karsten found some bad edge cases with how we handle slices in the bw auths. First, if there are no exits in a slice, it is simply skipped. Related, the last slice for a scanner may have very few members, and will probably also get skipped due to no exits.

Child Tickets

#20475newSetting bwscanner min_exits to 1 causes no exits to be selectedCore Tor/Torflow
#20504newWhen there is only one slice and one scanner, a bwauth runs a second empty sliceCore Tor/Torflow
#24223newtombwauths can output percentile ranges greater than 100Core Tor/Torflow

Change History (5)

comment:1 Changed 9 years ago by mikeperry

Also related to this is that we can output seemingly nonsensical result files at the end of the scan for percentile ranges of 99-102. The result files contain valid data, but perhaps we should have lumped it in with the previous slice if it either has no exits or is below a minimum size?

comment:2 Changed 3 years ago by teor

Severity: Blocker

This is a duplicate of some children of #17064, #20504, #20475.
Making this the parent ticket of the tickets that still need a fix.

comment:3 Changed 3 years ago by teor

Severity: BlockerNormal

Priorities and Severities in torflow are meaningless, setting them all to Medium/Normal.

comment:4 Changed 16 months ago by gaba

Owner: mikeperry deleted
Status: newassigned

comment:5 Changed 8 months ago by teor

Status: assignednew

Change tickets that are assigned to nobody to "new".

Note: See TracTickets for help on using tickets.