Skip to content

Feature request: logging #73

@iconoclasthero

Description

@iconoclasthero

ok, if i'm going to spend the time and energy to have something scan 67798 songs and it is going to report if there are errors with scanning those files, I want to be able to go back and find out why there were problems.

I tried to do blissify --config-path /library/music/.share/bliss-rs/config.json init /library/music &>>/var/log/mpd/blissify.log which should log it to file, but that seems to be a kludge at best.

Additionally, I'm at a loss to understand why there are 9211 lines telling me that there's a problem with the same exact song!

$ grep '/library/music/99-reggae/Peter Tosh/Peter Tosh & Bob Marley -- Wisdom (1998) (mp3)/02-01 - Bob Marley & The Wailers -- More Axe.m4a' /var/log/mpd/blissify.log |wc -l
9211

or even 17000:

$ grep "/library/music/Bob Marley/Bob Marley & The Wailers -- Talkin' Blues (1991) (mp3)/Bob Marley & The Wailers -- 01-04 - Burnin' & Lootin'.m4a" blissify.log|wc -l
17000

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