Open AveryUALibrary opened 4 days ago
Please leverage this checklist to ensure your code review is thorough before approving
@AveryUALibrary, thanks for this. Here are a few more things we need to get done (happy to add any/all of those to your fork):
GGUF
format, if I'm not mistaken; for most parts, these files are also hosted on HF, so maybe we can either add instructions but, better yet, use either direct HTTP calls to fetch the models or use HF tooling for that (if applicable).@AveryUALibrary, thanks for this. Here are a few more things we need to get done (happy to add any/all of those to your fork):
- Docs
- Tests
- Utility to fetch models - llama.CPP uses
GGUF
format, if I'm not mistaken; for most parts, these files are also hosted on HF, so maybe we can either add instructions but, better yet, use either direct HTTP calls to fetch the models or use HF tooling for that (if applicable).
The current implementation now contains updated docs and automatic fetching of hugging face models using Llama.from_pretrained
. No clue on how to implement testing for Chroma.
Description of changes
Implementation of Issue 2409
Summarize the changes made by this PR.
Test plan
How are these changes tested?
pytest
for python,yarn test
for js,cargo test
for rustDocumentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?