1. 20 Jan, 2022 1 commit
  2. 14 Jan, 2022 1 commit
  3. 12 Jan, 2022 1 commit
    • Volker Krause's avatar
      Fix the backend identifier · 76e3748d
      Volker Krause authored
      This was accidentally renamed as well when the test was renamed, making
      this always fail due to trying to use a non-existing backend.
      76e3748d
  4. 07 Jan, 2022 1 commit
  5. 05 Jan, 2022 3 commits
  6. 04 Jan, 2022 1 commit
  7. 03 Jan, 2022 1 commit
  8. 01 Jan, 2022 1 commit
  9. 21 Dec, 2021 1 commit
  10. 18 Dec, 2021 2 commits
  11. 17 Dec, 2021 2 commits
  12. 16 Dec, 2021 1 commit
  13. 13 Dec, 2021 6 commits
  14. 12 Dec, 2021 1 commit
  15. 09 Dec, 2021 2 commits
  16. 07 Dec, 2021 1 commit
  17. 02 Dec, 2021 3 commits
  18. 28 Nov, 2021 1 commit
  19. 27 Nov, 2021 1 commit
  20. 22 Nov, 2021 1 commit
  21. 16 Nov, 2021 1 commit
  22. 15 Nov, 2021 2 commits
  23. 14 Nov, 2021 1 commit
  24. 13 Nov, 2021 1 commit
  25. 12 Nov, 2021 1 commit
  26. 11 Nov, 2021 1 commit
  27. 09 Nov, 2021 1 commit
    • Volker Krause's avatar
      Prefer backends containing both ends of a journey · 4a6adbb2
      Volker Krause authored
      We still want to use backends containing only one side as a fallback, as
      those have a chance of working nevertheless (due to not detailed enough
      coverage area data), but those containing both sides are certainly better.
      
      Can reduce the amount of queries we do when no backend is explicitly
      selected.
      4a6adbb2