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
IntegrityError at /accounts/complete/google-oauth2/ #2074
Comments
It looks like the migration to 3.0 didn't really work well. Can you try dumping table structure for the |
bitten by nearly the same if i try to create a new user via weblate admin, createing a user via webinterface seems to be ok - as long no one hit the activation mail - weblate upgraded from 2.20 to 3 |
table structure
|
Looks like the |
That's swappable model and the database migration should have been performed here: https://github.com/WeblateOrg/weblate/blob/master/weblate/auth/migrations/0007_auto_20180509_0739.py So far it worked well in all my installations, so I'm really curious what might have gone wrong here. Can you check if there is other foreign key on to the |
So many ...
|
And
|
I just did another test.
No error in log when running migrations, However, the same error occurs when registering a user. |
Here is the test log
|
We need to figure out why weblate_auth.0007_auto_20180509_0739 is not doing it's job in this case. |
I think I've just fixed the issue. At least it works in screnario I was able to create to trigger such bug. It would be great if somebody else can confirm the fix (you need to start again from 2.20 to test this). Once the test is confirmed, it might make sense to create additional migration to cover broken 3.0 installs (though it still might be better for them to roll back to 2.20 and do the clean migration)....
|
I rolled back to 2.20 and then upgraded to 3.0. The problem has been solved. Thank you for making such an excellent application. |
Great, thanks for providing feedback! |
A have now the exactly same problem as we are gradually upgrading our old instance. I would prefer to fix it manually over to having to rollback again. And then a question, was this never updated in the pip sources? |
Disregard, I applied update to 3.0.1 and it seems to work => Could you update the Upgrade from 2.x part so that it points directly to 3.0.1 ? That would be great. |
It's already written there: https://docs.weblate.org/en/latest/admin/upgrade.html#upgrade-from-2-x |
OK somehow I managed to land on the upgrade to 3.0 page :) - no worries, everything is fine now. |
Steps to reproduce
Actual behaviour
Server Error
error log:
Server configuration
The text was updated successfully, but these errors were encountered: