-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
crash when using Discogs plugin #2965
Comments
Thank you for reporting! This looks like it might be related to #2893. @dbogdanov, can you please take a look at the traceback? Meanwhile, do you think it’s feasible to narrow down the album that’s causing this error? |
I ran it again and it looks like this is where it crashed:
(duplicate album prompt, and I chose to skip new)
looking this up at Discogs, both master release numbers 26833 and 27058 go to what is called a "master release" for "Human After All"; they have the same artist name and release title, so that is where I am supposing there is an issue. |
Great. The problem seems to be that the error handling code here assumed we were dealing with an album when we’re in fact dealing with a |
Correct, we should be using |
Great! Can you please send a pull request? |
Was this ever fixed? I'm getting the exact same issue... the last line reads as follows: |
I'm getting this problem too, any way to help this bug getting fixed ? |
@Yannovitch The best way to ensure it gets fixed is to help out yourself! You could try putting together a PR following the instructions from @dbogdanov above. |
Problem
Running an incremental import on a folder of files that may either be new or have duplicates in the library. When the import comes across a certain album-- not sure if it's precipitated by encountering the one that it is prompting me for, or if it's crashing on encountering another album it's processing in the background (which I'm pretty sure beets does?). I don't think it's the former, because
If I come across this, I'll turn off the discogs plugin and continue through the import. Later, if there are albums that I would have skipped because it wasn't found in MB, I'll run an import on those albums with discogs turned back on with no problem.
Running this command in verbose (
-vv
) mode:Led to this problem:
beginning of logfile...
(it continues even though I haven't given an input... I assume it's supposed to happen like that. It continues without incident I can see until the following event)
(occasionally I'll hit enter if beets doesn't appear to be prompting me - this is what happened here)
Setup
My configuration (output of
beet config
) is:The text was updated successfully, but these errors were encountered: