Skip to content
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

lp1846971: Fix database inconsistencies caused by LibraryScanner #2321

Merged
merged 3 commits into from Oct 22, 2019
Merged

lp1846971: Fix database inconsistencies caused by LibraryScanner #2321

merged 3 commits into from Oct 22, 2019

Conversation

uklotzde
Copy link
Contributor

@uklotzde uklotzde commented Oct 8, 2019

https://bugs.launchpad.net/mixxx/+bug/1846971

Mitigates serious bug reported in:
https://bugs.launchpad.net/mixxx/+bug/1603348
https://bugs.launchpad.net/mixxx/+bug/1846775 (very likely)
https://bugs.launchpad.net/mixxx/+bug/1846945 (marked as duplicate)

This is just a workaround and does not fix the actual cause for those inconsistencies! Restarting Mixxx and rescanning the library should discover the previously unreachable and ignored files.

Runs concurrently in the LibraryScanner thread and does not slow down the startup.

@uklotzde uklotzde added this to the 2.2.3 milestone Oct 8, 2019
@uklotzde
Copy link
Contributor Author

uklotzde commented Oct 8, 2019

There are many more database inconsistencies that pile up over time and that might cause any kind of undefined behavior. But I'm not able to invest a huge amount of time to satisfy the requirements of all stakeholders.

@uklotzde
Copy link
Contributor Author

Found another bug 3-year-old bug report that confirms this issue:

https://bugs.launchpad.net/mixxx/+bug/1603348

The attached database shows the same inconsistencies.

@uklotzde uklotzde changed the title Fix database inconsistencies caused by LibraryScanner lp1846971: Fix database inconsistencies caused by LibraryScanner Oct 20, 2019
@Be-ing
Copy link
Contributor

Be-ing commented Oct 21, 2019

Thank you for scaling back the scope of this. This looks like a reasonable way to handle those severe bugs.

@daschuer
Copy link
Member

LGTM, Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants