-
-
Notifications
You must be signed in to change notification settings - Fork 3k
Fix report scheduled emails not being sent with proper options #15052
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
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 5.2 #15052 +/- ##
============================================
+ Coverage 63.72% 63.75% +0.02%
- Complexity 34687 34698 +11
============================================
Files 2274 2275 +1
Lines 103776 103804 +28
============================================
+ Hits 66131 66176 +45
+ Misses 37645 37628 -17
🚀 New features to boost your workflow:
|
63cab7b
to
de05275
Compare
@biozshock could you please review CI ? Tests are failing. We'll close the next version in a few days. Thanks. |
e9d4a83
to
f86e4e0
Compare
@npracht That's a known issue with M5 tests ran between 21:00 and 2:00 UTC. Just need to restart the build. |
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.
Tested and fixed the issue - LGTM! :)
|
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.
Thanks for the fix. The code looks fine from my point of view. Can be merged
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.
Seems good to me
I am just bit aware of do that operation also for each email with attachment. With mass volume sending of email it's not necessary. Would consider add check if it's report attachment.
@biozshock WDYT?
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.
I approve it , it fixed what we need.
My concern is a note, break nothing
The test was failing because it was checking for messages after they were consumed and removed by messenger:consume. The fix checks for the queued message before consumption, which properly validates that the delayed transport functionality is working. - Remove flawed logic that checked for messages after messenger:consume - Add proper validation by checking for queued messages before consumption - This correctly tests the delayed transport feature from PR mautic#15052 - Files existence is validated at the appropriate time in the test flow
Description
PR fixes #14976
The PR also fixes a couple of issues (covered by test):
Failed to start the session because headers have already been sent by "/var/www/html/vendor/phpunit/phpunit/src/Util/Printer.php" at line 104.
📋 Steps to test this PR: