-
Notifications
You must be signed in to change notification settings - Fork 3.1k
feat: add support for vLLM response format in reranking logic and up… #5954
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
Conversation
Your cubic subscription is currently inactive. Please reactivate your subscription to receive AI reviews and use cubic. |
❌ Deploy Preview for continuedev failed. Why did it fail? →
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Iamshankhadeep thanks for looking into this! I'm thinking that instead of adding this extra logic to the BaseLLM class, we could just add a rerank method to the dedicated VLLM class. You can find an example of such a rerank method in the Voyage class.
Let me know if this makes sense or if I can explain further
@sestinj yup totally makes sense, |
2f655fa
to
c8d9d95
Compare
@sestinj should be ready for review. Let me know which issue I can work on next. thanks 🔥 |
✨ No issues found! Your code is sparkling clean! ✨ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the updates, this looks great!
Description
vLLM's rerank endpoint returns results.results instead of results.data like everyone else. Our code was trying to sort undefined.
her's the link Re-rank API
I aslo added proper TypeScript types (VllmRerankResponse), but build is failing because of that.
Checklist
fixes #5869