Re: [tor-bugs] #11965 [Tor]: 60-second pause bootstrapping with a bridge if you already have its descriptor

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#11965: 60-second pause bootstrapping with a bridge if you already have its
descriptor
------------------------+--------------------------------
     Reporter:  arma    |      Owner:
         Type:  defect  |     Status:  needs_revision
     Priority:  normal  |  Milestone:  Tor: 0.2.5.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-bridge
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------

Comment (by asn):

 Replying to [comment:7 arma]:
 > Replying to [comment:2 arma]:
 > > Which leads me to ask: is there anything that gets triggered when
 pt_proxies_configuration_pending() transitions from true to false, or is
 it likely we have a race condition here if it takes a while to configure
 our PTs?
 >
 > asn, what would you think about the following patch?
 >
 > <snip>
 >
 > Basically, we skip the "should we launch those two classes of dir
 fetches" steps not just when DisableNetwork is set, but also when you're
 using bridges and you don't have any useful descriptors yet, and when
 you're using bridges and you have pt_proxies_configuration_pending(). And
 then when should_delay_dir_fetches goes false, time_to_foo is before now,
 so they fire on the next run_scheduled_events().

 Sounds like it might work. I can test this approach in 2-3 days.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/11965#comment:16>
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