-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Refactor change stage campaign action to use batches #8969
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
Refactor change stage campaign action to use batches #8969
Conversation
Prevent unpublished emails from triggering unpublished campaigns.
Travis tests have failedHey @mohit-rocks, 2nd Buildif [ ${TRAVIS_PHP_VERSION:0:3} == "7.3" ]; then composer test -- --coverage-clover=coverage.xml && bash <(curl -s https://codecov.io/bash); else composer test; fi
TravisBuddy Request Identifier: c09b4c50-ba29-11ea-a74d-ef5d1a577ce8 |
@mohit-rocks Can you please update the tests for Travis to pass? Thanks! 😊 |
Codecov Re 8000 port
@@ Coverage Diff @@
## 3.3 #8969 +/- ##
============================================
+ Coverage 40.22% 40.27% +0.05%
- Complexity 34043 34044 +1
============================================
Files 1990 1990
Lines 105412 105419 +7
============================================
+ Hits 42404 42460 +56
+ Misses 63008 62959 -49
|
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.
Works 👍
@mohit-rocks I tested the bug on mautibox.com/staging to ensure I could replicate it before I applied the PR, and I do not experience the bug you are referencing. Take a look at this screencast: https://youtu.be/QG6JlcUF2QA In short:
@kuzmany were you able to reproduce the bug before you tested the PR? I think we need another test on this before we can decide whether the PR is required. |
@RCheesley Nope, I didn't test reproduce. I just test If both actions works properly after patch PR. I don't think before PR campaign was unpublished, but this PR improve other stuff, and this is reason why I approved. |
Original issue was already fixed in #8907 - nevertheless this PR might still be relevant. Maybe @alanhartless could explain a bit more like @kuzmany mentioned? |
Bumping to 3.1.1 due to the lack of response from original poster and PR author. |
@cla-bot check |
We require contributors to sign our Contributor License Agreement, and we do not have a record of your signature on file. In order for us to review and merge your code, please head over to https://www.mautic.org/contributor-agreement and complete the form. There may be a short delay while the team add you as a contributor - please be patient :). Any problems contact @RCheesley. CLA has not been signed by @mohit-rocks. |
The CLA Bot has been sent on a mission to check against the latest list and will be back shortly with its findings! |
@mohit-rocks @kuzmany this one has a conflict to be addressed and I am not sure if we got to the bottom of whether this is needed as a couple of testers were not able to reproduce the issue. @alanhartless could you review the issue and PR and give your thoughts? |
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 PR refactors the change stage campaign action to work in batches instead of one event at a time. So it improves performance but should not change the behavior.
Other than adding back the translation string this is good to go based on the code review. I did not test it but we (Acquia) use this in production for 2 years and Zdeno tested it.
@mohit-rocks try to keep the original author of the commit. It creates confusion on who is the author and who should answer questions about the code change.
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 covered the new methods with unit tests. This is good to go 👍
closes #8521
Original PR by Alan: #7812
Description:
If an email is unpublished or if a contact fails to move a stage, the event triggered a failure that would lead to notifications to users and campaigns being unpublished. This fixes that.
Steps to reproduce the bug:
Steps to test this PR:
List deprecations along with the new alternative:
List backwards compatibility breaks: