-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[Messenger] Mention the transport which failed during the setup command #49044
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 8000 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
[Messenger] Mention the transport which failed during the setup command #49044
Conversation
Hey! Thanks for your PR. You are targeting branch "6.3" but it seems your PR description refers to branch "6.3 for features / 5.4, 6.0, 6.1, or 6.2 for bug fixes". Cheers! Carsonbot |
src/Symfony/Component/Messenger/Tests/Command/SetupTransportsCommandTest.php
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a new feature, so please target 6.3
, thanks
OK, thanks for clarifying 👍 (sad that we're still on sf v5.4 😭 ) |
@OskarStark thanks for reviewing. I guess the failed CIs are not due to this PR (pSaml and appveyor reports errors not related to the messenger component) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGMT, I just have minor notes.
src/Symfony/Component/Messenger/Command/SetupTransportsCommand.php
Outdated
Show resolved
Hide resolved
src/Symfony/Component/Messenger/Command/SetupTransportsCommand.php
Outdated
Show resolved
Hide resolved
The transport name can help to further investigate the underlying reasons of the failure
Thank you @thePanz. |
Thanks @fabpot for merging! |
The transport name can help to further investigate the underlying reasons of the failure
I am not sure if this can be labelled as a new feature, but the addition from this PR can help to further investigate errors while setting up an application's transports.
At the moment, if an error occurs while setting up a transport just the exception is thrown, with no context on which transport was being setup.