AssertionError: object N not in DB during import
#4408
Comments
sampsyo
added
the
needinfo
|
It looks like the most recent album being imported (in the verbose log) is a re-import. Does importing that album reliably reproduce the error? |
|
No, reimporting just that album works fine. If I run the entire command again, I can reproduce the crash, but it takes roughly 6 hours before that happens. |
|
Wow, super strange. I'm not entirely sure how to dig in farther to understand what could be going wrong here. I think it is sort of suspicious that this arises when using your new |
|
I just encountered it again, this time without using the |
|
Ah, that could feasibly explain it… it would obviously be a goal for us to hide all of these inconsistent states through transactions, but in practice that can be hard to do, especially when replacing or re-importing things that are already in the database. If you happen to find some way to make this crash happen reliably in testing, please let us know so we can investigate further… |
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
|
No stale, it still happens. |
|
Alas, I suppose we're a bit stuck here… it's hard to look into if there's not an obvious way to reproduce the error "in vitro." Please do update the thread if you run across a repeatable way to encounter the problem. |
|
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I'm currently importing the remaining parts of my library into beets (the parts that haven't properly been tagged using musicbrainz). For this, I'm importing previously skipped paths from a logfile. To reduce the amount of manual work, I figured that as a first step I'll do a quiet import and let the autotagger find the best match. Hopefully, the resulting logfile will be shorter. Unfortunately, I'm hitting an
AssertionErrorapproximately 6 hours after I started importing.Problem
Running this command in verbose (
-vv) mode:Led to this problem:
truncated log output
Setup
OS: Arch Linux ARM (armv7l)
Python version: 3.10.5
beets version: 472c3ab (current upstream/master)
Turning off plugins made problem go away (yes/no): no
My configuration (output of
beet config) is: https://gist.github.com/Holzhaus/69660a9c2b20393eff9d4acb1fcf4f9cThe text was updated successfully, but these errors were encountered: