Looking at the history for the migrations code <https://github.com/django/django/commits/main/django/db/migrations>, the was https://github.com/django/django/commit/110001d0bbbabe2a5b57b14a59bd0e4b71bf2712#diff-e7df880bdc17c719e0332fa0cfbd4eff49bd481f638e34335a6311cfcd0ebc26 recently which adjusted AppConfigStub, so maybe related. (You could see if reverting that helps.)
On Thursday, 18 March 2021 at 15:39:04 UTC+1 Carlton Gibson wrote: > Hi. > > So, first off, thanks for testing! > > Initial thoughts: > > * We might need a bit more to be able to reproduce — are you able to > narrow down the problem? > * "Which migration it is varies between runs" — that sounds fun 😀 > * "Changing AppConfig.name..." — The AppConfig loading was reworked, it > could be that: > https://docs.djangoproject.com/en/dev/releases/3.2/#automatic-appconfig-discovery > > Can I ask you to get as close as you can to directions for a reproduce and > open a ticket on Trac? > https://code.djangoproject.com/newticket > > If you can't get to a reproduce, it's still worth opening a ticket with as > much info as you can: > * Maybe someone is able to say "Oh, it's this" > * Provides info for anyone else hitting this. > > Thanks again! > > Kind Regards, > > Carlton > > > On Thursday, 18 March 2021 at 15:26:23 UTC+1 HM wrote: > >> Changing AppConfig.name to just "app" leads to ModuleNotFoundError: No >> module named 'app'. >> >> Changing the path in INSTALLED_APPS to "prefix.app.apps.AppConfig" >> instead leads to the same NodeNotFoundError as before. >> >> On Thu, 18 Mar 2021 at 15:06, Hanne Moa <hann...@gmail.com> wrote: >> > >> > I have some migrations that runs/tests fine on Django 3.0 and 3.1, but >> > not on 3.2b1. >> > >> > There's a specific app whose migrations fail with: >> > >> > django.db.migrations.exceptions.NodeNotFoundError: Migration >> > prefix_app.000N_fooFoo dependencies reference nonexistent parent node >> > ('app', '000M_bar'). >> > >> > Which migration it is varies between runs, and note that the first app >> > label looks different than the second. Is there some new way to >> > auto-generate app labels that leads to this? >> > >> > In INSTALLED_APPS the app in question is by path: "prefix.app". In the >> > AppConfig, "name" is identical to the path, "prefix.app", while >> > "label" is "prefix_app". The models do not have an explicit tablename >> > set and in the database they have been created with >> > "app_modelnameinlowercase", not "prefix_app_modelnameinlowercase". >> > >> > >> > HM >> > -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/4424f465-3643-4a39-ac9b-f52bacbe48a8n%40googlegroups.com.
