Migration error when calling runserver after upgrade from PSA
See original GitHub issueGot this error when trying to upgrade from python-social-auth
, when running runserver
:
django.db.migrations.graph.NodeNotFoundError: Migration social_django.0005_auto_20160727_2333 dependencies reference nonexistent parent node (u'social_django', u'0004_auto_20160423_0400')
As far as I can see, there is a migration social_django/migrations/0004_auto_20160423_0400.py
, so not sure yet of the problem.
I am running Django 1.8.17.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:8
- Comments:13 (2 by maintainers)
Top Results From Across the Web
Can't migrate or makemigrations while trying to runserver
To solve this issue, try to comment out every code line in the specific view function, which uses the Gallery model, then create/run...
Read more >django-admin and manage.py
Shows the migration operations that will be performed for the given migrate command. --run-syncdb ¶. Allows creating tables for apps without migrations. While ......
Read more >VMware vCenter Server 6.0 Update 3g Release Notes
Important: Upgrade and migration paths from vCenter Server 6.0 Update 3g ... You might see the following error message: An internal error ......
Read more >CMD Error trying to run server? : r/Minecraft - Reddit
I downloaded the server.jar, ran the command line prompt (yes, I cd'd into the right folder) and got the following error: Error: A...
Read more >Plesk 10 update post-install failed
#3 /usr/local/psa/admin/smb/application/externals/Doctrine/Migration.php(230): Doctrine_Connection->fetchColumn('SELECT version ...') ... **** ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
If someone had used an old version (https://github.com/omab/python-social-auth) and changed it to the new version (https://github.com/python-social-auth/social-app-django), he would encounter the error.
I think this issue needs to be re-opened. I’m trying to do an upgrade and followed the migration guide and am getting the same exception:
I originally had installed and was using
python-social-auth==0.2.21
andDjango==1.7.11
and then installed the following:My django_migrations looks like this:
There’s possible solutions/hacks at https://github.com/omab/python-social-auth/issues/962 to get around this issue.
It seems like #4 should have fixed this, but for some reason it’s not working.