-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Post-update logging #3310
Post-update logging #3310
Conversation
…into post-update-logging
c5faa7e
to
0511043
Compare
The tests show that practically no useful output is being logged during the execution of the post-updates. This can be fixed by moving the post-update code into a batch operation inside Drush, similar to how it was done for |
Discussed with @pfrenssen and I will review this PR tomorrow morning so it can be quickly ready for the 9 stable release. |
* @param array $context | ||
* The batch context. | ||
*/ | ||
public function updateDoOnePostUpdate($function, &$context) |
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.
It seems that post updates have their own way of logging. Sad that we can not reuse the Drupal code.
Thank you. The exception message is now logged. Review done. @weitzman, this can be merged. |
Fix for #3308
This is postponed on #3302 and #3303.