CLI: llama-cli and llama-completion cosmetics #18053
Open
+10
−7
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.
Hello, I've just finished the last (I think) PR regarding separation of
llama-cliandllama-completionin docs and scripts. Here I tried to fix places wherellama-cliandllama-completionare absolutely obvious, so it is safe to make updates.llama-completionto.dockerignorellama-completionto the GitHub issue template.>implies non-interactive mode, so for nowllama-cliis not possible here)llama-completionindocs/backend/SYCL(llm_load_tensors: ...is the output ofllama-completion)llama-completiontodocs/backend/hexagon/READMEllama-completionindocs/backend/hexagon/developer(llama_model_loader: ...is the output ofllama-completion)llama-completioninscripts/fetch_server_test_models.pybecause it uses non-interactive mode.PS I found other places where I can't understand whether
llama-cliorllama-completionshould be used. I think maintainers of these docs may update them later.Related PRs: #17993, #18003