Skip to content

zune-jpeg: noisy log spam #131

@emilk

Description

@emilk

zune-jpeg uses very verbose log levels:

[2023-06-09T14:27:50Z INFO  zune_jpeg::decoder] Image encoding scheme =`Baseline DCT`
[2023-06-09T14:27:50Z INFO  zune_jpeg::headers] Image width  :1440
[2023-06-09T14:27:50Z INFO  zune_jpeg::headers] Image height :1920
[2023-06-09T14:27:50Z INFO  zune_jpeg::headers] Image components : 3
[2023-06-09T14:27:50Z INFO  zune_jpeg::components] Component ID:Y       HS:2 VS:2 QT:0
[2023-06-09T14:27:50Z INFO  zune_jpeg::components] Component ID:Cb      HS:1 VS:1 QT:1
[2023-06-09T14:27:50Z INFO  zune_jpeg::components] Component ID:Cr      HS:1 VS:1 QT:1
[2023-06-09T14:27:50Z INFO  zune_jpeg::decoder] Input colorspace YCbCr
[2023-06-09T14:27:50Z WARN  zune_jpeg::decoder] Headers decoded!
[2023-06-09T14:27:50Z INFO  zune_jpeg::decoder] Vertical and horizontal sub-sampling(2,2)
[2023-06-09T14:27:50Z INFO  zune_jpeg::mcu] Found EOI marker
[2023-06-09T14:27:50Z INFO  zune_jpeg::mcu] Finished decoding image

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions