Parece que algo pasó con las migraciones en el merge y ahora estamos con luz roja, podrías ver qué onda?
salida de travis:
CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0002_auto_20190911_0040, 0004_auto_20190406_2027 in asistencia).
To fix them run 'python manage.py makemigrations --merge'
Hacer el comando sugerido me crea un nuevo archivo de migración y al hacer manage.py migrate falla de todos modos con:
Apply all migrations: admin, asistencia, auth, contenttypes, sessions
Running migrations:
Applying contenttypes.0001_initial... OK
Applying auth.0001_initial... OK
Applying admin.0001_initial... OK
Applying admin.0002_logentry_remove_auto_add... OK
Applying admin.0003_logentry_add_action_flag_choices... OK
Applying asistencia.0001_initial... OK
Applying asistencia.0002_auto_20190406_1907...Traceback (most recent call last):
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 82, in _execute
return self.cursor.execute(sql)
File "D:\github\venv\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute
return self.cursor.execute(query, args)
File "D:\github\venv\lib\site-packages\MySQLdb\cursors.py", line 209, in execute
res = self._query(query)
File "D:\github\venv\lib\site-packages\MySQLdb\cursors.py", line 315, in _query
db.query(q)
File "D:\github\venv\lib\site-packages\MySQLdb\connections.py", line 226, in query
_mysql.connection.query(self, query)
MySQLdb._exceptions.OperationalError: (1050, "Table 'asistencia_asistencia' already exists")
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "D:\github\corp-0\zrstats\manage.py", line 15, in <module>
execute_from_command_line(sys.argv)
File "D:\github\venv\lib\site-packages\django\core\management\__init__.py", line 381, in execute_from_command_line
utility.execute()
File "D:\github\venv\lib\site-packages\django\core\management\__init__.py", line 375, in execute
self.fetch_command(subcommand).run_from_argv(self.argv)
File "D:\github\venv\lib\site-packages\django\core\management\base.py", line 323, in run_from_argv
self.execute(*args, **cmd_options)
File "D:\github\venv\lib\site-packages\django\core\management\base.py", line 364, in execute
output = self.handle(*args, **options)
File "D:\github\venv\lib\site-packages\django\core\management\base.py", line 83, in wrapped
res = handle_func(*args, **kwargs)
File "D:\github\venv\lib\site-packages\django\core\management\commands\migrate.py", line 234, in handle
fake_initial=fake_initial,
File "D:\github\venv\lib\site-packages\django\db\migrations\executor.py", line 117, in migrate
state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
File "D:\github\venv\lib\site-packages\django\db\migrations\executor.py", line 147, in _migrate_all_forwards
state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
File "D:\github\venv\lib\site-packages\django\db\migrations\executor.py", line 245, in apply_migration
state = migration.apply(state, schema_editor)
File "D:\github\venv\lib\site-packages\django\db\migrations\migration.py", line 124, in apply
operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
File "D:\github\venv\lib\site-packages\django\db\migrations\operations\models.py", line 92, in database_forwards
schema_editor.create_model(model)
File "D:\github\venv\lib\site-packages\django\db\backends\base\schema.py", line 307, in create_model
self.execute(sql, params or None)
File "D:\github\venv\lib\site-packages\django\db\backends\base\schema.py", line 137, in execute
cursor.execute(sql, params)
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 99, in execute
return super().execute(sql, params)
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 67, in execute
return self._execute_with_wrappers(sql, params, many=False, executor=self._execute)
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 76, in _execute_with_wrappers
return executor(sql, params, many, context)
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 84, in _execute
return self.cursor.execute(sql, params)
File "D:\github\venv\lib\site-packages\django\db\utils.py", line 89, in __exit__
raise dj_exc_value.with_traceback(traceback) from exc_value
File "D:\github\venv\lib\site-packages\django\db\backends\utils.py", line 82, in _execute
return self.cursor.execute(sql)
File "D:\github\venv\lib\site-packages\django\db\backends\mysql\base.py", line 71, in execute
return self.cursor.execute(query, args)
File "D:\github\venv\lib\site-packages\MySQLdb\cursors.py", line 209, in execute
res = self._query(query)
File "D:\github\venv\lib\site-packages\MySQLdb\cursors.py", line 315, in _query
db.query(q)
File "D:\github\venv\lib\site-packages\MySQLdb\connections.py", line 226, in query
_mysql.connection.query(self, query)
django.db.utils.OperationalError: (1050, "Table 'asistencia_asistencia' already exists")
Parece que algo pasó con las migraciones en el merge y ahora estamos con luz roja, podrías ver qué onda?
salida de travis:
Hacer el comando sugerido me crea un nuevo archivo de migración y al hacer
manage.py migrate
falla de todos modos con: