Opened 22 months ago

Last modified 22 months ago

#24094 new defect

measured bw percentage is always 100

Reported by: Sebastian Owned by: tom
Priority: Medium Milestone:
Component: Core Tor/Torflow Version:
Severity: Normal Keywords:
Cc: Actual Points:
Parent ID: #17064 Points:
Reviewer: Sponsor:

Description

Using tor 0.3.1.7, I get this right from the first start:

NOTICE[Tue Oct 31 12:45:15 2017]:Measured 100.0% of all tor nodes (100.0% of previous consensus bw).

the bwscan-file is produced but only contains 400 lines.

Child Tickets

Change History (8)

comment:1 Changed 22 months ago by tom

I'm told the hack to avoid this it to either stick to 0.2.9 or earlier, or set usemicrodescriptors 0

comment:2 Changed 22 months ago by teor

The current tor behaviour is being tracked in #24110. But the workaround should be ok until we upgrade to a better controller library.

comment:3 Changed 22 months ago by teor

Status: newneeds_review

See my github branch bug24094 for a fix for this.

comment:4 Changed 22 months ago by teor

Status: needs_reviewmerge_ready

We've decided this is trivial and syntactically correct, so I'm going to merge it as soon as my access comes through.

comment:5 Changed 22 months ago by teor

Status: merge_readyneeds_information

Workaround merged to master as f38c085, setting back to "needs information" in case we want to fix the underlying bug in torflow/pytorctl.

comment:6 Changed 22 months ago by teor

Status: needs_informationnew

I hate state machines

comment:7 Changed 22 months ago by teor

Parent ID: #17064

Might be a cause of #17064

comment:8 Changed 22 months ago by teor

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

Note: See TracTickets for help on using tickets.