Fix bolt:setup by running doctrine scripts in new context #3649
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Doctrine caches the found migrations (which is logical), but that breaks when you generate a new migration and then try to run it in the same Application context. This was not shown on the console due to the usage of the NullOutput. By migrating to the existing Script helper we resolve the issue as each invocation now receives it's own Application context without cached migrations.
bobvandevijver
force-pushed
the
3648-fix-setup
branch
from
cef7383 to
7f31857
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Doctrine caches the found migrations (which is logical), but that breaks when you generate a new migration and then try to run it in the same Application context. This was not shown on the console due to the usage of the NullOutput. By migrating to the existing Script helper we resolve the issue as each invocation now receives it's own Application context without cached migrations.
Fixes #3648