1. 17 Apr, 2019 1 commit
  2. 14 Mar, 2019 3 commits
  3. 07 Mar, 2019 1 commit
  4. 21 Feb, 2019 1 commit
  5. 01 Feb, 2019 1 commit
  6. 19 Dec, 2018 2 commits
  7. 18 Dec, 2018 1 commit
  8. 14 Dec, 2018 1 commit
  9. 16 Nov, 2018 1 commit
  10. 27 Aug, 2018 1 commit
  11. 15 Jun, 2018 1 commit
  12. 06 Jun, 2018 2 commits
  13. 05 Jun, 2018 1 commit
  14. 22 May, 2018 1 commit
  15. 19 Apr, 2018 1 commit
  16. 17 Apr, 2018 1 commit
  17. 28 Feb, 2018 1 commit
  18. 23 Feb, 2018 1 commit
  19. 23 Jan, 2018 1 commit
  20. 28 Nov, 2017 1 commit
  21. 27 Nov, 2017 1 commit
  22. 05 Oct, 2017 1 commit
  23. 24 Aug, 2017 1 commit
  24. 06 Jul, 2017 2 commits
  25. 21 Jun, 2017 1 commit
  26. 20 Jun, 2017 2 commits
  27. 22 Feb, 2017 1 commit
  28. 21 Feb, 2017 1 commit
  29. 16 Feb, 2017 1 commit
  30. 09 Jan, 2017 1 commit
  31. 21 Oct, 2016 1 commit
  32. 01 Sep, 2016 2 commits
  33. 23 Jun, 2016 1 commit
    • Ard Schrijvers's avatar
      HIPPLUG-1329 [Forward port 3.1] make sure every worker has its own urlset · e80b956a
      Ard Schrijvers authored
      The Urlset object should have to think about synchronization. It is the code
      that uses the Urlset that shouldn't expect the Urlset to be thread-safe (just
      like a HashSet isn't thread-safe. It make much more sense to not give all the
      workers a reference to the same urlset object but all have their own
      
      A seperate note is that I really think the worker should not extend from
      Thread and a lot of the complex logic can be replaced by a simple executer service
      
      (cherry picked from commit 031750fa)
      e80b956a