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.

Sign up for GitHub

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

Jump to bottom

chore: use text instead of content for ChatMessage in Llama.cpp, Langfuse and Mistral #1238

Merged
merged 1 commit into from
Dec 10, 2024
Merged

chore: use text instead of content for ChatMessage in Llama.cpp, Langfuse and Mistral #1238

merged 1 commit into from
Dec 10, 2024

Conversation

anakin87
Copy link
Member

@anakin87 anakin87 commented Dec 9, 2024 •
edited
Loading

Related Issues

Proposed Changes:

  • use text instead of content for ChatMessage in Llama.cpp, Langfuse and Mistral
  • I did the changes in a single PR because we only need a release for Llama.cpp (for others, I'm only changing the tests)

How did you test it?

CI

Checklist

@anakin87 anakin87 changed the title chore: use text instead of content for ChatMessage in **Llama.cpp**, Langfuse and Mistral chore: use text instead of content for ChatMessage in Llama.cpp, Langfuse and Mistral Dec 9, 2024
@anakin87 anakin87 marked this pull request as ready for review December 9, 2024 17:02
@anakin87 anakin87 requested a review from a team as a code owner December 9, 2024 17:03
@anakin87 anakin87 requested review from davidsbatista and removed request for a team December 9, 2024 17:03
@anakin87 anakin87 merged commit 54a0573 into main Dec 10, 2024
22 checks passed
@anakin87 anakin87 deleted the chatmessage-text-2 branch December 10, 2024 13:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@davidsbatista davidsbatista davidsbatista approved these changes

Assignees
No one assigned
Labels
integration:langfuse integration:llama_cpp integration:mistral
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@anakin87 @davidsbatista