tor/changes/ticket28912

  o Major bugfixes (relay, directory):
    - A connection serving directory information wouldn't get reactivated after
      the first chunk of data was sent (usually 32KB). Tor now always activate
      the main loop event that goes through these connections as long as at
      least one connection is still active. Fixes bug 28912; bugfix on
      0.3.4.1-alpha. Patch by "cypherpunks3".
mainloop: Reactivate the linked connection event with a non empty list Linked connections aren't woken up by libevent due to I/O but rather artificially so we can, by chunks, empty the spooled object(s). Commit 5719dfb48f87a54aeb5982ff03345303bc058ebb (in 0.3.4.1-alpha) made it that the schedule_active_linked_connections_event would be only called once at startup but this is wrong because then we would never go through again the active linked connections. Fortunately, everytime a new linked connection is created, the event is activated and thus we would go through the active list again. On a busy relay, this issue is mitigated by that but on a slower relays or bridge, a connection could get stuck for a while until a new directory information request would show up. Fixes #28717, #28912 2018-12-21 17:17:45 +01:00			`o Major bugfixes (relay, directory):`
			`- A connection serving directory information wouldn't get reactivated after`
			`the first chunk of data was sent (usually 32KB). Tor now always activate`
			`the main loop event that goes through these connections as long as at`
			`least one connection is still active. Fixes bug 28912; bugfix on`
			`0.3.4.1-alpha. Patch by "cypherpunks3".`