1. 06 Mar, 2019 1 commit
    • juga  's avatar
      Release v1.0.4 · 1bb248b8
      juga authored
      because there was a commit missing between `1.0.3` and `1.0.4-dev0`
      and what is released as `1.0.3` has version `1.0.4-dev0` and it
      can not be fixed now.
  2. 05 Mar, 2019 8 commits
  3. 03 Mar, 2019 1 commit
  4. 28 Feb, 2019 9 commits
  5. 27 Feb, 2019 5 commits
  6. 26 Feb, 2019 5 commits
    • juga  's avatar
      tests: CB.build_circuit now returns a tuple · 54c5db04
      juga authored
      Change tests added in #28897 with the changes introduced in #28736.
    • juga  's avatar
      scanner: stop threads when there're not destinations · 3fe64b06
      juga authored
      Exit the scanner with error stoping threads first when there is not
      any functional destination, since the destinations can not be recovered.
      After merging #28897, `stop_threads` can be used (instroduced in #28869).
    • juga  's avatar
      destination: remove unused code · 883307ba
      juga authored
    • juga  's avatar
      destination: record consecutive failures · 84e5d82c
      juga authored
      Add methods to store consecutive destination failures and retrieve
      the destinations that are still functional.
      Since destinations can fail because of Tor circuits, it's not count
      individual failures but consecutives one.
      Also exit with error if there are no functional destinations left.
      The maximum number of consecuitve failures is set to 10, but it
      may need to be changed depending on the percentage of circuits and
      requests that fail.
    • juga  's avatar
      destination: stop running twice usability tests · d33ac8f6
      juga authored
      in every measurement.
      This removes the need for an extra lock for every measurement
      It should also not be depending on a time interval, but on the
      number of failures detected.
      Not counting number of failures since it would need to modify the
      destination or list of at runtime. It should be done in a future
      Fixes bug #28897. Bugfix v0.3.0
  7. 25 Feb, 2019 4 commits
  8. 24 Feb, 2019 1 commit
  9. 23 Feb, 2019 6 commits