NodeNotFoundError Migration error(Python 3) about django-river

[psychok7]

@javrasya let me know if you need more information

[psychok7]

After fiddling around i think i may have found the root problem and a workaround.

so basically my 0001_initial.py was generating this

    dependencies = [
        ('river', '0007_auto_20161013_1149'),
    ]

This migration does not exist in the source code (and i am not sure were is it coming from) so i changed the migration to:

    dependencies = [
        ('river', '0006_auto_20160524_0439'),
    ]

I noticed then that there was one migration left to do (the actual 0007)

root@8b7595afac0e:/code# python3 manage.py makemigrations --settings=smal.settings.local
System check identified some issues:

WARNINGS:
river.ProceedingMeta.groups: (fields.W340) null has no effect on ManyToManyField.
river.ProceedingMeta.parents: (fields.W340) null has no effect on ManyToManyField.
Migrations for 'river':
  /usr/local/lib/python3.5/dist-packages/river/migrations/0007_auto_20161013_1150.py:
    - Alter field parents on proceedingmeta
root@8b7595afac0e:/code# python3 manage.py migrate --settings=smal.settings.local
System check identified some issues:

WARNINGS:
river.ProceedingMeta.groups: (fields.W340) null has no effect on ManyToManyField.
river.ProceedingMeta.parents: (fields.W340) null has no effect on ManyToManyField.
Operations to perform:
  Apply all migrations: admin, auth, authtoken, authtools, contenttypes, djcelery, ip_geocoding, local_accommodation, qualifications, river, sessions, sites, users
Running migrations:
  Applying river.0007_auto_20161013_1150... OK
root@8b7595afac0e:/code#

Hope this helps

[javrasya]

I think there is a problem with python 3, because here is the result with python 2.7

    dependencies = [
        ('river', '0006_auto_20160524_0439'),
    ]

I could reproduce your case with python 3. I am looking at it.

[javrasya]

I create migrations with python 2.7 most of time. In a weird way, python2.7 could't detect a migration which is 0007 one somehow python3 can detect. I will create this migration with python3 and commit it.

[javrasya]

@psychok7 could you please test it with master branch, it supposed to be fixed, I commited the missing migration file.

[javrasya]

Please, do not forget to install it with --upgrade to delete previous django-river to reset migrations. Because you created 0007 in your workspace right.

[psychok7]

@javrasya oh ok, i will try to test it tomorrow or monday morning and let you know

[psychok7]

@javrasya i tested the latest commit against a database without django river but with data and everything is working.