1. 21 Nov, 2025 1 commit
  2. 19 Nov, 2025 2 commits
  3. 17 Nov, 2025 1 commit
  4. 11 Nov, 2025 1 commit
  5. 10 Nov, 2025 1 commit
  6. 08 Nov, 2025 1 commit
  7. 07 Nov, 2025 1 commit
  8. 31 Oct, 2025 1 commit
  9. 22 Oct, 2025 1 commit
  10. 17 Oct, 2025 1 commit
  11. 16 Oct, 2025 2 commits
  12. 08 Oct, 2025 1 commit
  13. 07 Oct, 2025 1 commit
  14. 30 Sep, 2025 1 commit
  15. 24 Sep, 2025 1 commit
  16. 22 Sep, 2025 1 commit
  17. 19 Sep, 2025 2 commits
  18. 18 Sep, 2025 1 commit
  19. 11 Sep, 2025 1 commit
  20. 10 Sep, 2025 1 commit
  21. 02 Sep, 2025 2 commits
  22. 30 Aug, 2025 1 commit
  23. 19 Aug, 2025 1 commit
  24. 15 Aug, 2025 1 commit
  25. 22 Jul, 2025 1 commit
  26. 07 Jul, 2025 1 commit
  27. 01 Jul, 2025 1 commit
  28. 14 Jun, 2025 1 commit
  29. 30 May, 2025 1 commit
  30. 29 May, 2025 1 commit
  31. 20 May, 2025 1 commit
  32. 19 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. 17 Mar, 2025 1 commit
  35. 11 Mar, 2025 1 commit
  36. 09 Mar, 2025 1 commit