Skip to content
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

Merged
merged 12 commits into from
Jan 18, 2018
Merged

Post-update logging #3310

merged 12 commits into from
Jan 18, 2018

Conversation

pfrenssen
Copy link
Member

Fix for #3308

This is postponed on #3302 and #3303.

@pfrenssen
Copy link
Member Author

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 hook_update_N() updates in UpdateDBCommands::updateDoOne().

@pfrenssen pfrenssen changed the title WIP: Post-update logging Post-update logging Jan 18, 2018
@claudiu-cristea
Copy link
Member

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)
Copy link
Member

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.

@claudiu-cristea
Copy link
Member

claudiu-cristea commented Jan 18, 2018

Thank you. The exception message is now logged. Review done. @weitzman, this can be merged.

@weitzman weitzman merged commit 9ad698f into master Jan 18, 2018
@weitzman weitzman deleted the post-update-logging branch January 18, 2018 21:25
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.

3 participants