New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doctrine Migration Bundle (bin/console make:migration ?) runs its own checks for the Messenger component settings #49120
Comments
By the way, this is the stack trace I posted on the other repo before being forwarded here:
|
Can you create a small example application that allows to reproduce your issue? |
I am going to close here for now due to the lack of feedback. Please let us know when you have more information and we can consider to reopen. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
5.4.12
Description
Good day,
As per my report here doctrine/DoctrineMigrationsBundle#485 it seems this issue I am experiencing with the Doctrine Bundle and the Messenger component working with the AMQP implementation are caused by this pull request #36655
It seems the Messenger.yaml file works file when warming up the cache but it throws an error with the Doctrine Bundle and generating migrations - the lines that cause the error seem to be:
Any ideas here?
According to
bin/console --version
I am running Symfony 5.4.12Thanks,
How to reproduce
I have a project including the Messenger AMQP vendor as well as the Doctrine Pack.
I get the error when I set up the AMQP transport with the
options.exchange
key and try to generate adiff
migration:Possible Solution
I'm open to suggestions, but based on doctrine/DoctrineMigrationsBundle#485 it seems to be an issue with the update merged here #36655
Additional Context
No response
The text was updated successfully, but these errors were encountered: