[BUG] Chroma crash with the new numpy version - update requirements.txt

[itayB]

Description of changes

Summarize the changes made by this PR.

• Improvements & Bug fixes
  • NumPy just released their next major version and chroma is crashing

    import chromadb
  File "/usr/local/lib/python3.12/site-packages/chromadb/__init__.py", line 3, in <module>
    from chromadb.api.client import Client as ClientCreator
  File "/usr/local/lib/python3.12/site-packages/chromadb/api/__init__.py", line 7, in <module>
    from chromadb.api.models.Collection import Collection
  File "/usr/local/lib/python3.12/site-packages/chromadb/api/models/Collection.py", line 7, in <module>
    import chromadb.utils.embedding_functions as ef
  File "/usr/local/lib/python3.12/site-packages/chromadb/utils/embedding_functions.py", line 7, in <module>
    from chromadb.api.types import (
  File "/usr/local/lib/python3.12/site-packages/chromadb/api/types.py", line 102, in <module>
    ImageDType = Union[np.uint, np.int_, np.float_]
                                         ^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/numpy/__init__.py", line 397, in __getattr__
    raise AttributeError(
AttributeError: `np.float_` was removed in the NumPy 2.0 release. Use `np.float64` instead.. Did you mean: 'float16'?

Suggesting locking before version 2 as a first Aid

[github-actions]

Reviewer Checklist

Please leverage this checklist to ensure your code review is thorough before approving

Testing, Bugs, Errors, Logs, Documentation

• Can you think of any use case in which the code does not behave as intended? Have they been tested?
• Can you think of any inputs or external events that could break the code? Is user input validated and safe? Have they been tested?
• If appropriate, are there adequate property based tests?
• If appropriate, are there adequate unit tests?
• Should any logging, debugging, tracing information be added or removed?
• Are error messages user-friendly?
• Have all documentation changes needed been made?
• Have all non-obvious changes been commented?

System Compatibility

• Are there any potential impacts on other parts of the system or backward compatibility?
• Does this change intersect with any items on our roadmap, and if so, is there a plan for fitting them together?

Quality

• Is this code of a unexpectedly high quality (Readability, Modularity, Intuitiveness)

[HammadB]

Thanks for flagging we will cut a new release this week to patch this

[atroyn]

Thanks for raising this. Was successfully able to reproduce, and this is due to Chroma using now deprecated generic types in some of our multimodal datatypes:

chroma/chromadb/api/types.py

Line 102 in cc790a7

ImageDType = Union[np.uint, np.int_, np.float_]

This is an easy fix, but unfortunately on further testing I found that onnxruntime which is upstream of us is also broken by numpy 2.0.

Pinning the version is probably the way to go! Let's keep the previous requirement to be above 1.22.5, while introducing this new one too.

[itayB]

Thanks for raising this. Was successfully able to reproduce, and this is due to Chroma using now deprecated generic types in some of our multimodal datatypes:

chroma/chromadb/api/types.py

Line 102 in cc790a7

ImageDType = Union[np.uint, np.int_, np.float_]

This is an easy fix, but unfortunately on further testing I found that onnxruntime which is upstream of us is also broken by numpy 2.0.

Pinning the version is probably the way to go! Let's keep the previous requirement to be above 1.22.5, while introducing this new one too.

done, thanks

[itayB]

same happens here now: #2356

[atroyn]

same happens here now: #2356

I didn’t see this in my testing but will check again.

[HammadB]

Closing this in favor of #2360 since we needed a few additional changes and I didn't want to hold up the fix on a review cycle - I really appreciate the fix here @itayB