1. 01 May, 2025 1 commit
  2. 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
  3. 28 Apr, 2025 1 commit
  4. 26 Apr, 2025 1 commit
  5. 25 Apr, 2025 2 commits
    • Harrison Saturley-Hall's avatar
    • Graham King's avatar
      chore: Publish Model Deployment Card to NATS (#799) · d346782c
      Graham King authored
      This will allow an ingress-side pre-processor to see it without needing a model checkout.
      
      Currently pre-processing is done in the worker, which has access to the model deployment card ("MDC") files (`config.json`, `tokenizer.json` and `tokenizer_config.json`) locally. We want to move the pre-processor to the ingress side to support KV routing. That requires ingress side (i.e the HTTP server), on a different machine than the worker to be able to see those three files.
      
      To support that this PR makes the worker upload the contents of those files to the NATS object store, and publishes the MDC with those NATS urls to the key-value store. 
      
      The key-value store has an interface so any store (nats, etcd, redis, etc) can be supported. Implementations for memory and NATS are provided.
      
      Fetching the MDC from the store, doing pre-processing ingress side, and publishing a card backed by a GGUF, are all for a later commit.
      
      Part of #743 
      d346782c
  6. 21 Apr, 2025 2 commits
  7. 18 Apr, 2025 1 commit
  8. 17 Apr, 2025 2 commits
  9. 12 Apr, 2025 1 commit
  10. 11 Apr, 2025 1 commit
  11. 09 Apr, 2025 1 commit
  12. 04 Apr, 2025 2 commits
  13. 03 Apr, 2025 2 commits
  14. 02 Apr, 2025 1 commit
  15. 01 Apr, 2025 1 commit
  16. 31 Mar, 2025 1 commit
  17. 28 Mar, 2025 1 commit
  18. 24 Mar, 2025 1 commit
  19. 19 Mar, 2025 1 commit
    • Graham King's avatar
      chore: Don't depend on openssl (#292) · 7c3fd5c9
      Graham King authored
      This makes the Rust parts all use ring / rustls library instead of local install of openssl. It's a step on the journey to being statically linked.
      
      Pieces:
      - `tokenizers` and `mistralrs` now support rustls (mistralrs by default, tokenizers with feature flag).
      - Move shared dependencies up into workspace
      - New `rand` crate has some renames for future rust
      - Ensure the dependency doesn't creep back in by enforcing it with cargo deny.
      7c3fd5c9
  20. 18 Mar, 2025 1 commit
  21. 17 Mar, 2025 1 commit
  22. 16 Mar, 2025 1 commit
  23. 14 Mar, 2025 2 commits
  24. 13 Mar, 2025 1 commit
  25. 11 Mar, 2025 2 commits
  26. 10 Mar, 2025 1 commit
  27. 09 Mar, 2025 5 commits
  28. 08 Mar, 2025 2 commits