-
-
Notifications
You must be signed in to change notification settings - Fork 242
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
Daemon locking improvements #4735
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #4735 +/- ##
===========================================
- Coverage 85.26% 27.68% -57.59%
===========================================
Files 340 335 -5
Lines 24428 24157 -271
Branches 4631 4585 -46
===========================================
- Hits 20829 6688 -14141
- Misses 2189 16766 +14577
+ Partials 1410 703 -707 ☔ View full report in Codecov by Sentry. |
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.
Looks like a nice and neat solution to a thorny problem. I like the change that breaks open311_update_missing_data
out into its own thing - it was definitely getting a bit heavy in places.
One little copy/paste thing in the SQL migration is all, otherwise 👍
Add a processing state so the daemons still do not clash, but unlock the row during actual processing in case that takes a long time. Changes to prevent race conditions in processing coming up next.
Introduce a new open311_update_missing_data cobrand hook to be used to add/save any missing data to the report before sending via Open311, that is wrapped in a transaction. open311_extra_data_include should now only be used to add columns for sending, not to edit the row in any way. When sending via Open311, any changes made pre-send (after update_missing_data) are now automatically discarded after sending.
bfd6b2b
to
d977312
Compare
[skip changelog]