-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zune-jpeg: noisy log spam #131
Comments
will do in a few |
Moved them to trace in 6bf3480 Will move other libraries to trace as time goes by |
Thanks for fixing this in |
cleaning them one by one about to make a big release in a few days with most logs changed to trace (and some new formats) will address this beforehand |
etemesi254
added a commit
that referenced
this issue
Aug 15, 2023
Replace `info!` with `trace!` for all decoders to reduce log verbosity for the library that may depend on the decoder. Addresses #131 (comment) Signed-off-by: caleb <etemesicaleb@gmail.com>
etemesi254
added a commit
that referenced
this issue
Oct 21, 2023
Replace `info!` with `trace!` for all decoders to reduce log verbosity for the library that may depend on the decoder. Addresses #131 (comment) Signed-off-by: caleb <etemesicaleb@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
zune-jpeg
uses very verbose log levels:This means any user of the library will have to manually mute the logs from
zune-jpeg
if they want any sort of log hygiene.I suggest lowering all these to TRACE, or DEBUG at most. Users can always opt-in to more verbose logging with
RUST_LOG=zune-jpeg=trace
if they want it (e.g. when debugging zune-jpeg).The text was updated successfully, but these errors were encountered: