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

[Bug]: Upgrading Binner file database from v2.3.0 to v2.5.1 fails on migrate #185

Closed
replaysMike opened this issue May 4, 2023 · 1 comment
Assignees
Labels
bug Something isn't working
Milestone

Comments

@replaysMike
Copy link
Owner

replaysMike commented May 4, 2023

Binner version

v2.3.0

Operating System

Linux

Describe the bug and the steps to reproduce it

When starting Binner, it throws an error failing to upgrade the database.

The problem was - likely due to an older bug - there was a duplicate partType in the old database and when it was upgraded it failed to handle this condition gracefully.

A PR is being submitted for the fix, which will group and filter duplicates out on migrate.

Would you like to attach your appsetings.json configuration?

No response

Screenshots or Videos (Optional, but they help!)

Are you able to contribute a PR? (No is ok!)

Yes, I am also opening a PR that solves the problem along side this issue

@replaysMike replaysMike added the bug Something isn't working label May 4, 2023
@replaysMike replaysMike added this to the v2.5.2 milestone May 4, 2023
@replaysMike replaysMike self-assigned this May 4, 2023
@replaysMike
Copy link
Owner Author

Fixed in v2.5.2

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant