Repository navigation
embed: MODEL line names the embedding model - #6
Merged
Merged
Conversation
…s reports A side seat answers beside the server's chat model, so /props model_path named the wrong model. Take the answer's "model", else --model, else the one embedding entry of a multi-model /v1/models.
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
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.
A side seat embeds beside the chat model, but the MODEL line came from /props model_path, so it showed the chat model (reported on bloomery #190).
The line now uses the response's
model, else--model, else the single embedding entry when /v1/models lists several. Test covers both with a two-model /v1/models fixture../scripts/check.shpasses.