-
Notifications
You must be signed in to change notification settings - Fork 47
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
Database migration failure #241
Comments
Interesting, thank you for the bug report! I'm looking into this now. Given the source of the error, I think this may be a bug in the underlying gorm library (github.com/go-gorm/gorm) which I did upgrade the version of last week. |
Ok, it looks like the root cause here is a mismatch of versions where we were using an older version of pgx and the gorm postgres driver, but a newer version of gorm. #243 should fix this, I'm going to let it run through all the tests on GH actions and then will release it ASAP. I'll also follow up in a separate change to improve our test coverage to ensure we prevent this from happening again in the future. |
* Add test coverage to prevent issues like #241 in the future * Add debugging * Fix location of HISHTORY_COMPOSE_TEST var * Enable tmate for failures * update * Re-comment tmate
Version 0.310.20240830
The text was updated successfully, but these errors were encountered: