Detect Mixtral's slightly different format#1214
Merged
abetlen merged 1 commit intoabetlen:mainfrom Feb 23, 2024
Merged
Conversation
abetlen
approved these changes
Feb 23, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Currently in main Mixtral will not work reliably for chat completions because the slightly different Mixtral chat format string is not detected in the metadata, so this adds the right string and checks that too so it can then use the existing format_mistral_instruct method which does seem to work well enough.
I think this should help make using Mixtral more obvious.
I suspect this will address #1202
@abetlen