[tor-bugs] #2878 [Tor Client]: Confusing order of log messages if Tor is restarted after a some downtime

[Tor Bug Tracker & Wiki]

#2878: Confusing order of log messages if Tor is restarted after a some downtime
------------------------+---------------------------------------------------
 Reporter:  Sebastian   |          Owner:                    
     Type:  defect      |         Status:  new               
 Priority:  minor       |      Milestone:  Tor: 0.2.2.x-final
Component:  Tor Client  |        Version:                    
 Keywords:              |         Parent:                    
   Points:              |   Actualpoints:                    
------------------------+---------------------------------------------------

Comment(by nickm):

 How old was the datadir?

 I think the timeline here is something like:

      * We start with an older consensus and some matching descriptors.
 The consensus is old enough that we want to replace it, but not so old
 that we refuse to use it at all.
      * We start fetching a new consensus
      * We build some circuits and announce that we're bootstrapped.
      * The new consensus arrives, and we realize all our old server
 descriptors are unlisted.  Now we know no good servers, so we declare that
 we're unbootstrapped, and start fetching server descriptors
      * The new server descriptors arrive; we decide that we can build
 circuits again
      * We build circuits, and declare that we're bootstrapped.

 Can we think of a better behavior here?  Most improvements that I can
 think of right now are subtle enough that I'd prefer that they wait for
 0.2.3, but if we can come up with something easy and safe, it could go
 into 0.2.2 IMO.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/2878#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online