Thanks to visit codestin.com
Credit goes to github.com

Skip to content

[Mailer] Include all transports' debug messages in RoundRobin transport exception #48126

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

Merged
merged 1 commit into from
Dec 14, 2022

Conversation

mixdf
Copy link

@mixdf mixdf commented Nov 6, 2022

Q A
Branch? 5.4
Bug fix? yes
New feature? no
Deprecations? no
Tickets ...
License MIT
Doc PR N/A

Description

The RoundRobin Mail transport does not include inner transports' debug messages in case of failure, which makes it very difficult to reason about the failures.

This PR attempts to add that debug information to the thrown TransportException.

In the process of fixing this issue, I discovered that one of the existing tests is incorrect. The last assertion is never executed and the test passes regardless of the assertion state. The test was also fixed.

Note that although this issue exists in https://github.com/symfony/symfony/tree/5.0, I wasn't able to apply the same patch to it since the behavior of the transport (specifically the cursor property) was different. I can open a new PR to fix the same issue for that branch as well.

@carsonbot
Copy link

Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

  • Always add tests
  • Keep backward compatibility (see https://symfony.com/bc).
  • Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
  • Features and deprecations must be submitted against the 6.2 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

@mixdf
Copy link
Author

mixdf commented Nov 9, 2022

The failing CI build is not related to the changes in this PR (another module) and passes locally. Not sure if the test is flaky.

@nicolas-grekas nicolas-grekas modified the milestones: 6.0, 5.4 Dec 14, 2022
@nicolas-grekas nicolas-grekas changed the base branch from 6.0 to 5.4 December 14, 2022 15:29
@nicolas-grekas nicolas-grekas force-pushed the 6.0 branch 2 times, most recently from 7ddfd21 to cd43856 Compare December 14, 2022 15:42
@nicolas-grekas
Copy link
Member

Thank you @mixdf.

@nicolas-grekas nicolas-grekas merged commit d38ef67 into symfony:5.4 Dec 14, 2022
@mixdf mixdf deleted the 6.0 branch December 14, 2022 15:52
@mixdf
Copy link
Author

mixdf commented Dec 14, 2022

@nicolas-grekas Thanks for merging this change 🙂

@fabpot fabpot mentioned this pull request Dec 16, 2022
This was referenced Dec 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants