1. 06 Jan, 2026 1 commit
  2. 02 Jan, 2026 1 commit
  3. 03 Dec, 2025 1 commit
  4. 25 Nov, 2025 1 commit
  5. 20 Nov, 2025 1 commit
  6. 17 Nov, 2025 1 commit
  7. 11 Nov, 2025 1 commit
  8. 10 Nov, 2025 2 commits
  9. 06 Nov, 2025 1 commit
  10. 28 Oct, 2025 1 commit
  11. 27 Oct, 2025 1 commit
  12. 23 Oct, 2025 1 commit
  13. 17 Oct, 2025 1 commit
  14. 13 Oct, 2025 1 commit
  15. 07 Oct, 2025 2 commits
  16. 25 Sep, 2025 1 commit
  17. 16 Sep, 2025 1 commit
  18. 30 Aug, 2025 1 commit
  19. 22 Aug, 2025 1 commit
  20. 15 Aug, 2025 1 commit
  21. 13 Aug, 2025 2 commits
  22. 22 Jul, 2025 1 commit
  23. 11 Jun, 2025 1 commit
  24. 23 May, 2025 1 commit
  25. 21 May, 2025 1 commit
  26. 09 May, 2025 1 commit
  27. 07 May, 2025 1 commit
  28. 29 Apr, 2025 1 commit
    • Graham King's avatar
      chore: Split PushRouter from Client (#817) · a1a10365
      Graham King authored
      In a distributed system we don't know if the remote workers need pre-processing done ingress-side or not. Previously Client required us to decide this before discovering the remote endpoints, which was fine because pre-processing was worker-side.
      
      As part of moving pre-processing back to ingress-side we need to split this into two steps:
      - Client discovers the endpoints, and (later PR) will fetch their Model Deployment Card.
      - PushRouter will use the Model Deployment Card to decide if they need pre-processing or not, which affects the types of the generic parameters.
      
      Part of #743
      a1a10365
  29. 26 Apr, 2025 1 commit
  30. 12 Apr, 2025 1 commit
  31. 07 Mar, 2025 1 commit
  32. 25 Feb, 2025 1 commit
  33. 24 Feb, 2025 1 commit
  34. 18 Feb, 2025 1 commit
  35. 12 Feb, 2025 1 commit
  36. 11 Feb, 2025 1 commit
  37. 05 Feb, 2025 1 commit