-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
Fix first user message #6471
Fix first user message #6471
Conversation
Hi! I started running the integration tests on your PR. You will receive a comment with the results shortly. |
Trigger by: Pull Request (integration-test label on PR #6471) Total cost: USD 0.11
Integration Tests Report (DeepSeek) Total cost: USD 0.00
Integration Tests Report Delegator (Haiku) Total cost: USD 0.00
Integration Tests Report Delegator (DeepSeek) Total cost: USD 0.00
Integration Tests Report VisualBrowsing (DeepSeek) Total cost: USD 0.00
Download testing outputs (includes both Haiku and DeepSeek results): Download |
The DeepSeek API can take a LOOOONG time right now, locally too, I'll check what's up, but I don't think it has anything to do with this PR. 😅 The fix did eventually work locally. |
@@ -200,7 +200,6 @@ def index(): | |||
Running the updated file: | |||
<function=execute_bash> | |||
<parameter=command> | |||
<parameter=command> |
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.
This one is confusing the llm
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.
LGTM! And i agree with the comments robert has bring up -- thanks for fixing these :D
End-user friendly description of the problem this fixes or functionality that this introduces
Fix DeepSeek error on consecutive user messages.
Give a summary of what the PR does, explaining any non-trivial design decisions
Users are getting an error about "consecutive" user messages with the new Deepseek. Reported and WIP on the litellm repo:
This PR proposes to refactor the first user message more aligned with the other prompt enhancement we have, and fix it for us, anyway, while we're at it.
Link of any specific issues this addresses
Fix #6459
Fix #6443
Reported on slack
To run this PR locally, use the following command: