-
Notifications
You must be signed in to change notification settings - Fork 6
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
Feature request: logging #73
Comments
I noticed that the songs with errors are recorded... Realistically, that is most of what I want out of the log. Is there a facility to output these aside from directly quering the db, e.g.,
maybe a |
Hi! Thanks for submitting, and very good point, you should be able to see errors without having to fiddle with the SQL. I've made a branch at #76 - As a side-note, would it be possible to send me the failing files? Especially interested in the ones that make blissify segfault, as this should not happen, and I'm hoping I can fix this, but I'd be also interested in looking at the others and see what's up there too. Cheers! |
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!
or even 17000:
The text was updated successfully, but these errors were encountered: