[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #4011 [Tor Relay]: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has a normal consensus

#4011: 0.2.3.3 relay won't fetch microdesc consensus on startup if it already has
a normal consensus
-----------------------+----------------------------------------------------
 Reporter:  arma       |          Owner:                    
     Type:  defect     |         Status:  new               
 Priority:  major      |      Milestone:  Tor: 0.2.3.x-final
Component:  Tor Relay  |        Version:  Tor: 0.2.3.3-alpha
 Keywords:             |         Parent:                    
   Points:             |   Actualpoints:                    
-----------------------+----------------------------------------------------

Comment(by arma):

 Probably the "right" answer here is to turn
 time_to_download_next_consensus into an array based on flavor. Then we can
 have a time for each flavor, and move the "if" clause down a few lines
 into the "for" loop in update_consensus_networkstatus_downloads().

 I spent a while thinking about hackish ways too, e.g.
 time_to_download_next_consensus should be now if there's any consensus
 whose flavor we don't have. But I think they are all too hackish.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/4011#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs