[tor-bugs] #10993 [Tor]: Fails to reconnect after connection loss when only one bridge is configured

[Tor Bug Tracker & Wiki]

#10993: Fails to reconnect after connection loss when only one bridge is configured
--------------------+---------------------
 Reporter:  lunar   |          Owner:
     Type:  defect  |         Status:  new
 Priority:  normal  |      Milestone:
Component:  Tor     |        Version:
 Keywords:          |  Actual Points:
Parent ID:          |         Points:
--------------------+---------------------
 When configured to use only a single bridge, if the connection to that
 bridge is lost (which typically happen when suspending or hoping from one
 network to another), tor will not try to reconnect even when the bridge is
 reachable available again.

 At notice level, you can see a loop of:
 {{{
 smartlist_choose_node_by_bandwidth(): Empty routerlist passed in to old
 node selection for rule weight as guard
 should_delay_dir_fetches(): delaying dir fetches (no running bridges
 known)
 compute_weighted_bandwidths(): Empty routerlist passed in to consensus
 weight node selection for rule weight as guard
 }}}

 I don't think this happen when there is more than one bridge configure but
 I'm not 100% sure at this time.

 I also have the feeling that this did not happen with version 0.2.3, but
 I'm not 100% sure either.

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