Malformed Log File #4937
Replies: 1 comment 1 reply
-
Thanks for reporting this! Looking into the error handling for this log-file parser, it looks like we are doing a pretty crude job with catching and reporting errors: Lines 107 to 111 in e10b955 A It should be possible to learn more from the traceback in verbose mode. Trying Line 99 in e10b955 And in turn, the problem with that is that it's just splitting the end of the log-file line on
…because we actually did log three different paths, separated by
In conclusion, this is definitely a bug in beets. The log file parser can't distinguish between To work around this for now, you might consider manually editing your log file and deleting lines where |
Beta Was this translation helpful? Give feedback.
-
I'm doing my best to work out beets as a complete novice, and I've had a lot of luck so far! However, I am now trying to import skipped directories from my logfile, and I'm not sure where to go from here.
I'm getting the error
error: malformed logfile F:/Music/BEETS_IMPORTER_LOG: Can't mix absolute and relative paths
which, after a bit of research, I think means that the logfile contains a mix of directories (likeF:\Music\blah blah
and\Music\blah blah
. I've had a look through the log file and I can't see this occurring anywhere in the file though.Would appreciate being pointed in the right direction! I've attached the logfile (saved it as .txt first) and below is a copy of what Powershell is spitting out at me:
BEETS_IMPORTER_LOG.txt
Beta Was this translation helpful? Give feedback.
All reactions