fix: update pyproject.toml dependencies for vector processing

[skamenan7]

What does this PR do?

Updates pyproject.toml dependencies to fix vector processing compatibility issues.

closes: #3495

Test Plan

Tested llama stack server with faiss vector database:

1. Built and ran server: llama stack build --distro starter --image-type venv --image-name llamastack-faiss
2. Tested file upload: Successfully uploaded PDF via /v1/openai/v1/files
3. Tested vector operations:
   - Created vector store with faiss backend
   - Added PDF to vector store
   - Performed semantic search queries

[leseb]

I'm confused, the starter image has:

  - provider_id: rag-runtime
    provider_type: inline::rag-runtime

which pulls both pypdf and chardet.
However, I do agree that this is a miss. Especially if someone is not using inline::rag-runtime.

Btw using started I don't repro your issue.

[mattf]

can these be put in llama_stack/providers/registry/vector_io.py ?

[leseb]

can these be put in llama_stack/providers/registry/vector_io.py ?

for all providers?

EDIT: at least the ones that speak openai vector store

[mattf]

can these be put in llama_stack/providers/registry/vector_io.py ?

for all providers?

EDIT: at least the ones that speak openai vector store

yes, make them deps for providers that use them

[ashwinb]

for Matt's comment

in prov config registry

[skamenan7]

Thanks all for your comments. Yes, I encountered this when I tried to use openai compatible endpoint for file upload flow without rag runtime.

[skamenan7]

Hi @mattf , @ashwinb , @leseb, I will go ahead and add chardet and pypdf to their pip_packages for all the following vector IO providers that have
optional_api_dependencies=[Api.files]

  1. inline::meta-reference (line 26) - pip_packages=["faiss-cpu"]
  2. inline::faiss (line 36) - pip_packages=["faiss-cpu"]
  3. inline::sqlite-vec (line 89) - pip_packages=["sqlite-vec"]
  4. inline::sqlite_vec (line 297) - pip_packages=["sqlite-vec"] (deprecated)
  5. remote::chromadb (line 310) - pip_packages=["chromadb-client"]
  6. inline::chromadb (line 352) - pip_packages=["chromadb"]
  7. remote::pgvector (line 396) - pip_packages=["psycopg2-binary"]
  8. remote::weaviate (line 508) - pip_packages=["weaviate-client"]
  9. inline::qdrant (line 548) - pip_packages=["qdrant-client"]
  10. remote::qdrant (line 601) - pip_packages=["qdrant-client"]
  11. remote::milvus (line 614) - pip_packages=["pymilvus>=2.4.10"]
  12. inline::milvus (line 820) -
  pip_packages=["pymilvus[milvus-lite]>=2.4.10"]

[leseb]

please remove the changes in uv.lock and we can move fw with this

[leseb]

please remove uv.lock changes

[skamenan7]

Hi @leseb , I took care of uv.lock comment you pointed out. Thanks.

[leseb]

victory!

addressed, deps in registry now