Repository navigation
Say what is missing when a container session has no model or no index - #24
Merged
Merged
Conversation
Started from the container's shell with no model configured, SPEAR opened on a local server that is not there and showed its model as a question mark; the first question would have failed. The command now stops and says what to put in the configuration file. The startup check called a tree the user had just registered a corpus missing from the baked index, to be fixed by rebuilding the image. It now tells the image's own corpora, where that is a fault, from the user's, which are simply not indexed yet, and says how to index one from a session rather than with a host command the image does not have.
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.
Two misleading outputs of
spear-chatin the container shell:model: ? (local llama-server). The command now stops with what to put in~/.config/spear/local.conf.spear-index, which the image does not have. The check now separates the image's corpora (a fault) from the user's (not indexed yet) and names/reindex.Tried in the image on a workspace with seven registered sub-trees; the suite passes.