1. 21 Feb, 2019 8 commits
  2. 12 Feb, 2019 3 commits
  3. 05 Feb, 2019 1 commit
  4. 01 Feb, 2019 1 commit
  5. 23 Jan, 2019 3 commits
  6. 18 Jan, 2019 2 commits
  7. 09 Jan, 2019 1 commit
  8. 08 Jan, 2019 3 commits
  9. 07 Jan, 2019 6 commits
  10. 04 Jan, 2019 6 commits
  11. 03 Jan, 2019 3 commits
  12. 21 Dec, 2018 1 commit
    • David Goulet's avatar
      mainloop: Reactivate the linked connection event with a non empty list · 2420e84b
      David Goulet authored
      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 5719dfb4 (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
      2420e84b
  13. 11 Dec, 2018 2 commits