-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support for ⚡ Groq API #637
Conversation
adding the inspect_history
@ivarflakstad thank you for the PR. |
@someshfengde deserves the thanks😊 |
yes sure @insop will do it. :) |
Hi @insop I've added the documentation for the same :) |
Thank you @someshfengde , looks good to me. |
@insop removed comment also resolved merge conflicts |
Very great, can't handle myself the see the mistral8x7b tests. Groq is very cheap, can it be 0,27$ for million tokens?! Great great great ! Thank you @someshfengde |
When I run the script. I get dspy cannot find GROQ. I pip install dspy-ai. Am I missing anything? |
@pfa34488 Yes you have to integrate the changes yourself! This workflow is waiting approval |
Thanks so much! I see the module at curieo.org/dspy under dsp modules; I see from .groq_client import * and the groq_client.py file. I am not sure how to add. Do i find the pip install dspy-ai or git clone (https://github.com/curieo-org/dspy.git) or something else? Please help! |
Yes there is 8 file change in this PR, do it yourself or wait until it is implemented |
Thanks so much. Checks fail because this has imports that are always on but are only needed for those that use this class. Please see how cohere and many other modules do this, for a different pattern: import on demand. |
I got it LoL. You guys are sharp. From Newbe |
Hi @pfa34488 you can clone a branch from repo with branch initial-groq-support. Sorry currently you can't work with the main branch I'm resolving an error for The Together api over main. |
Welcome 🤗 |
It's still not integrated into the main branch. It'll soon be integrated 🙂 |
Yes sure will do it 👍🏻 |
Hi @someshfengde , the CI tests seem to still fail. Could you run these following commands to fix it? Run Tests failure: Check Ruff Fix (formatting) failure: Build Poetry failure (You will have to make changes to fix the error triggered below):
|
I've also left another comment for removing the extraneous files from .gitignore |
Also, can you remove all the related Together changes? seems they have been added in some extra commits I didn't see before but they are unrelated to the Groq LM in this PR and are modifying the integrated dspy.Together LM. Let me know if you have any questions about this (but these changes could possibly be impacting the test failures too!) |
Hi @arnavsinghvi11 Removed the together related files, removed the gitignore added files too. Updated the poetry lock with poetry lock --no-update Thanks for the review |
Hi @someshfengde , the tests pass but there are still conflicts. Can you check if its a merge conflict on your end? if not, I will checkout and merge the changes to main through command line. |
@arnavsinghvi11 |
Happy to merge here once conflicts are gone |
Hi @okhat for every other commit in poetry lock file will cause the merge conflict I've been resolving these conflicts lot's of times already 😢 |
Ah got it. Why not just remove/revert the lock and other files you don’t need to change? You just need to change like 4-5 files |
yes just a sec will do it rn |
@okhat it's done |
Hi @someshfengde , it's still failing the poetry tests. Can you run |
I've ran this many times we are falling behind since every new push to the main repo will cause merge issues in this one? |
After merging and running the commands, are there any updates you need to commit? seems like that should fix it or removing the poetry.lock which has extraneous changes. |
@arnavsinghvi11 I've fixed the poetry lock for now |
Closing since #773 is merged. Thanks again @someshfengde ! |
Now we can use Groq API within dspy.
Makes querying to LLMs lot faster. 💨
Thanks @ivarflakstad for helping me debug.
Usage:
Output