1. 02 Dec, 2025 1 commit
  2. 25 Nov, 2025 1 commit
  3. 13 Nov, 2025 1 commit
  4. 10 Nov, 2025 1 commit
  5. 08 Nov, 2025 1 commit
  6. 31 Oct, 2025 1 commit
  7. 28 Oct, 2025 2 commits
  8. 24 Oct, 2025 1 commit
  9. 23 Oct, 2025 1 commit
  10. 21 Oct, 2025 1 commit
  11. 17 Oct, 2025 1 commit
  12. 11 Oct, 2025 1 commit
  13. 10 Oct, 2025 1 commit
  14. 26 Sep, 2025 1 commit
  15. 17 Sep, 2025 1 commit
  16. 16 Sep, 2025 1 commit
  17. 03 Sep, 2025 1 commit
  18. 29 Aug, 2025 1 commit
  19. 28 Aug, 2025 1 commit
  20. 25 Aug, 2025 1 commit
  21. 22 Aug, 2025 1 commit
  22. 15 Aug, 2025 1 commit
  23. 14 Aug, 2025 1 commit
  24. 11 Aug, 2025 1 commit
  25. 07 Aug, 2025 2 commits
  26. 05 Aug, 2025 2 commits
  27. 28 Jul, 2025 1 commit
  28. 23 Jul, 2025 1 commit
  29. 22 Jul, 2025 1 commit
  30. 08 Jul, 2025 1 commit
  31. 11 Jun, 2025 1 commit
  32. 23 May, 2025 1 commit
  33. 04 Apr, 2025 1 commit
    • Graham King's avatar
      feat: Python decorator dynamo_worker takes optional `static` parameter without etcd (#494) · 88ad3425
      Graham King authored
      Adds `@dynamo_worker(static = True)` to create a static worker which has a predictable name and hence does not require discovery or `etcd` to be running. There can only be a single static worker per namespace / component / endpoint trio.
      
      This contrasts with the default dynamic `dynamo_worker` endpoints we have now, which get a unique random name (based on namespace/component/endpoint), and are discovered by ingress components using etcd.
      
      Also change the hello_world example to use `dynamo_worker(static = True)` so that it is exercised and demonstrated somewhere.
      
      For NIM.
      88ad3425
  34. 02 Apr, 2025 1 commit
  35. 09 Mar, 2025 1 commit
  36. 06 Mar, 2025 1 commit
  37. 25 Feb, 2025 1 commit