[2.0.0-2.0.4] Bake migration_snapshot throws exception when trying to mark migrated #428
Labels
Comments
I was the one asking about the issue on Slack @challgren, you might want to edit your answer so the Wouter you tagged won't get bothered with updates ;) Is there a way to work around this until it's fixed? |
Run |
I transferred the issue to correct place and I wanna convert this shell/task (mark_migrated) to command soon |
Also the schema lock is not being updated which causes problems for further migration_diff generation. |
As a workaround modify SnapshotTrait.php and replace 2 lines around line 66 with $this->_io->out('Marking the migration ' . $fileName . ' as migrated...');
debug($dispatchCommand);
//$this->dispatchShell($dispatchCommand); And around line 87 with:
This will output two commands that you can use and run manually (bin/cake .....) to achieve normal behavior |
PR welcome if this is still an issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
So I created a new app following the instructions on cakephp/app and when baking my first migration using the
bin/cake bake migration_snapshot Initial
the following exception is generated. However the migration file is generated but the phinx tables are not generated and the migration is not marked as applied. I'm not sure if this should be reported in cakephp/cakephp or cakephp/migrations or here. However if I dobin/cake migrations mark_migrated
the phinx table is generated and the migration is mark as migrated. I know @WrDX on Slack was also experiencing this issue.When I first created my original 4.x app I was able to successfully bake a migration and it be run. That migration is dated 20191222 so I'm not sure if something changed in the past month that would be causing this new error.
The text was updated successfully, but these errors were encountered: