google-code-export / beets

Automatically exported from code.google.com/p/beets
MIT License
0 stars 0 forks source link

Crash when importing a release. #418

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What's the problem? How can I reproduce it?

Basically I have beet crashing everytime I run it on a specific release. I'll 
privately email you a link for dowloading it in order to reproduce the bug. 
Meanwhile, I believe the stacktrace is probably a good start to investigate:

Traceback (most recent call last):
  File "/usr/bin/beet", line 9, in <module>
    load_entry_point('beets==1.0b16', 'console_scripts', 'beet')()
  File "/usr/lib/python2.7/site-packages/beets/ui/__init__.py", line 764, in main
    subcommand.func(lib, config, suboptions, subargs)
  File "/usr/lib/python2.7/site-packages/beets/ui/commands.py", line 804, in import_func
    timid, query, incremental, ignore, per_disc_numbering)
  File "/usr/lib/python2.7/site-packages/beets/ui/commands.py", line 698, in import_files
    per_disc_numbering = per_disc_numbering,
  File "/usr/lib/python2.7/site-packages/beets/importer.py", line 915, in run_import
    pl.run_parallel(QUEUE_SIZE)
  File "/usr/lib/python2.7/site-packages/beets/util/pipeline.py", line 243, in run
    out = self.coro.send(msg)
  File "/usr/lib/python2.7/site-packages/beets/importer.py", line 562, in initial_lookup
    task.set_candidates(*autotag.tag_album(task.items, config.timid))
  File "/usr/lib/python2.7/site-packages/beets/autotag/match.py", line 439, in tag_album
    va_likely)
  File "/usr/lib/python2.7/site-packages/beets/autotag/hooks.py", line 157, in _album_candidates
    out.extend(mb.match_album(artist, album, len(items)))
  File "/usr/lib/python2.7/site-packages/beets/autotag/mb.py", line 245, in match_album
    assert albuminfo is not None
AssertionError

Original issue reported on code.google.com by chm.duquesne on 10 Aug 2012 at 7:21

GoogleCodeExporter commented 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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
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

GoogleCodeExporter commented 9 years ago
I was suspecting the same thing. Thank you for investigating!

Original comment by chm.duquesne on 13 Aug 2012 at 8:49