common: improve verbosity level definitions#17630
Merged
Merged
Conversation
ggerganov
approved these changes
Dec 1, 2025
| " - 2: warning\n" | ||
| " - 3: info\n" | ||
| " - 4: debug\n" | ||
| "(default: 3)\n", |
Member
There was a problem hiding this comment.
string_format the actual default value
Anico2
added a commit
to Anico2/llama.cpp
that referenced
this pull request
Jan 15, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
blime4
referenced
this pull request
in blime4/llama.cpp
Feb 5, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
Seunghhon
pushed a commit
to Seunghhon/llama.cpp
that referenced
this pull request
Apr 26, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
ljubomirj
pushed a commit
to ljubomirj/llama.cpp
that referenced
this pull request
May 6, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
my-other-github-account
pushed a commit
to my-other-github-account/llama.cpp
that referenced
this pull request
May 15, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
my-other-github-account
pushed a commit
to my-other-github-account/llama.cpp
that referenced
this pull request
May 15, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
phibya
pushed a commit
to ziee-ai/llama.cpp
that referenced
this pull request
May 29, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
fewtarius
pushed a commit
to fewtarius/CachyLLama
that referenced
this pull request
May 30, 2026
* common: improve verbosity level definitions * string_format * update autogen docs
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.
(This change is part of the plan to use server code inside CLI)
The current log verbosity is not very useful as it only has 3 levels: (-1) logs nothing, (0) default, (1) debug
This PR adds more hierarchy so that "the higher verbosity number, more stuff get logged":
For CLI and most applications, the output (for example, generated text, json, csv, etc) can be written using
LOG_LEVEL_OUTPUT, which is equivalent to theLOG(...)macroThe default verbosity for future CLI application (server based) will ideally be ERROR, this is because WARN also log some redundant stuff in the middle of the conversation