Replies: 1 comment
-
I don't see a use case for this - separating the common logs from the llama logs is the intended behavior. You can disable common logs with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to propose to add a logging callback mechanism similar to
llama
andggml
incommon
. This will not only further unify the logging system, but it will also allow the user to controlllama
,ggml
andcommon
logs using a callback.As of
master
, if the user sets the callback viallama_log_set
, thecommon
logs will be agnostic to this callback. For example, if the user were to specify a callback viallama_log_set
that prevents any logs from being printed out, there would still be some logs fromcommon
being outputted tostderr
.For the example above, the user can redirect
stderr
to/dev/null
to parse out the remaining logs, but this is not ideal since this approach masks real errors to the user. Therefore, I believe it would be beneficial to have a logging callback mechanism incommon
.I'm happy to do the work on the implementation, and I'm open to thoughts, comments and/or suggestions?
Thank you.
Beta Was this translation helpful? Give feedback.
All reactions