-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
lastgenre fails during a full library run #2525
Comments
Correction: this particular failure (exact stack trace) appears now during import as well. This probably means that the problem has been triggered by some db change, as I haven't updated |
Yikes; looks like trouble. To help narrow this down, would you mind trying this out while disabling some of your lastgenre config options (e.g., prefer_specific and fallback)? That might help us understand whether a specific option is causing the crash. |
Your intuition was correct: this failure only happens if I set |
OK, that helps! I can't reproduce the crash here just with |
I've fiddled with With prefer_specific: yes
canonical: yes
With prefer_specific: no
canonical: yes Setting |
Hmm, is this a subcase of #2459 ? |
Hmm; yes! The traceback does seem to indicate the same root bug here. The additional evidence here will certainly be useful; thank you! |
Simple run of
beet lastgenre
seems to fail before any genre is being fetched.I believe the plugin has been otherwise working during importing of files, as I see genres set in the library, and they're different from what the files came with. An attempt to fetch genres for the whole library, however, fails as described above.
Setup
plugins: lastgenre
alone.My configuration (output of
beet config
) is:Please tell me if you need any more information from me.
The text was updated successfully, but these errors were encountered: