Closed GoogleCodeExporter closed 9 years ago
I mailed you the link to the folder.
The crash is produced by running "beet import" on it. My ~/.beetconfig:
[beets]
directory: ~/music
library: ~/beetslibrary.blb
import_log: ~/beets.log
per_disc_numbering: yes
import_move: yes
[beets]
plugins: chroma fetchart scrub
[paths]
default: $albumartist/$album%aunique{}/$track $title
singleton: Non-Album/$artist/$title
comp: Compilations/$album%aunique{}/$track $title
Original comment by chm.duquesne
on 10 Aug 2012 at 7:39
FYI this is a release I added myself to the musicbrainz db. But since I messed
up in the process, at some point I decided to cancel all my edits and
re-created the release again on musicbrainz. After that, I started having beets
crashing.
Original comment by chm.duquesne
on 10 Aug 2012 at 7:47
The musicbrainz database has been updated and I can no longer reproduce this
bug with the same album.
Original comment by chm.duquesne
on 11 Aug 2012 at 8:33
It looks like this was likely caused by some temporary inconsistency in the
state of the MusicBrainz database. Specifically, it looks like the album was
found by the search server but not by direct ID lookup -- these two databases
should be synchronized.
I've pushed a fix, but I can't test it without reproducing this particular
quirk.
Original comment by adrian.sampson
on 13 Aug 2012 at 5:37
I was suspecting the same thing. Thank you for investigating!
Original comment by chm.duquesne
on 13 Aug 2012 at 8:49
Original issue reported on code.google.com by
chm.duquesne
on 10 Aug 2012 at 7:21