Opened 5 years ago

Last modified 12 months ago

#9045 new defect

Don't let the call frequency of update_networkstatus_downloads() depend on TorTestingNetwork

Reported by: ln5 Owned by:
Priority: Low Milestone: Tor: unspecified
Component: Core Tor/Tor Version:
Severity: Normal Keywords: tor-client, directory, testing, safety, correctness, cleanup
Cc: Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

In #8532 we start calling update_networkstatus_downloads() more often when TorTestingNetwork is set. That shouldn't be necessary but is the safe thing to do for now. It should go away at some point though.

Child Tickets

Change History (7)

comment:1 Changed 5 years ago by nickm

Milestone: Tor: unspecifiedTor: 0.2.5.x-final

Specifically, we should call it with equal frequencies in both cases (so that testing doesn't diverge too much from reality). See #8532 for a little discussion of why I'm too cowardly to try making it "one second" in production right now though.

comment:2 Changed 5 years ago by nickm

Keywords: tor-client directory added

comment:3 Changed 4 years ago by nickm

Milestone: Tor: 0.2.5.x-finalTor: 0.2.???

comment:4 Changed 19 months ago by teor

Milestone: Tor: 0.2.???Tor: 0.3.???

Milestone renamed

comment:5 Changed 18 months ago by nickm

Keywords: tor-03-unspecified-201612 added
Milestone: Tor: 0.3.???Tor: unspecified

Finally admitting that 0.3.??? was a euphemism for Tor: unspecified all along.

comment:6 Changed 12 months ago by nickm

Keywords: tor-03-unspecified-201612 removed

Remove an old triaging keyword.

comment:7 Changed 12 months ago by nickm

Keywords: testing safety correctness cleanup added
Severity: Normal
Note: See TracTickets for help on using tickets.