Skip to content
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: Gemini system instructions not sent with null RAG_API_URL #4920

Merged
merged 1 commit into from
Dec 18, 2024

Conversation

alex-torregrosa
Copy link
Contributor

Summary

System instructions were not being sent to gemini models when RAG_API_URL was not set, as the original promptPrefix was not being populated.

Change Type

Please delete any irrelevant options.

  • Bug fix (non-breaking change which fixes an issue)

Testing

Run a gemini model with RAG_API_URL not set and ask it "list available artifact types". It will not be able to provide a list

Checklist

Please delete any irrelevant options.

  • My code adheres to this project's style guidelines
  • I have performed a self-review of my own code
  • I have commented in any complex areas of my code
  • I have made pertinent documentation changes
  • My changes do not introduce new warnings
  • Local unit tests pass with my changes

@alex-torregrosa alex-torregrosa changed the title fix: Gemini system instructions not sent 🐛 fix: Gemini system instructions not sent with null RAG_API_URL Dec 14, 2024
System instructions were not being sent to gemini models when RAG_API_URL was not set, as the original promptPrefix was not being populated.
@danny-avila danny-avila merged commit 000641c into danny-avila:main Dec 18, 2024
1 check passed
owengo pushed a commit to openwengo/LibreChat that referenced this pull request Dec 20, 2024
…ny-avila#4920)

System instructions were not being sent to gemini models when RAG_API_URL was not set, as the original promptPrefix was not being populated.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants