Contrib.social

Make late runtime processor compatible with drush

Open on Drupal.org →
Created on 3 August 2020, over 4 years ago
Updated 17 July 2024, 4 months ago

When executing a script or cron through drush, the late runtime processor never executes.

The cause for this seems to lie in the fact that the late runtime processor only listens to the FINISH_REQUEST kernel event. This event, however, is never executed in a console (such as drush) context.

Is there a specific reason for this? If not, a possible solution would be to also add a listener to Symfony's terminate event.

✨ Feature request
Status

Fixed

Version

3.0

Component

Code

Created by

🇧🇪Belgium rp7

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Comment 4 months ago →
    🇩🇰Denmark kasperg

    In case someone is interested I have added support for configuring whether to disable the late runtime processor when running CLI commands in ✨ Make late runtime processor compatible with drush Fixed .

  • Comment 1 day ago →
    achap 🇦🇺

    I'm getting "MySQL server has gone away errors" after long running drush operations like search api indexing and running migrations with the lateruntime processor enabled. Those operations can put thousands of cache tags in the queue and it seems like it is trying to process many of them at the end of the request, or at the end of batches which is resulting in a packet size greater than max_allowed_packet. My max_allowed_packet setting is already quite high and I don't have much room to increase so I agree with the other comments that it would be better to at least have the option to disable it for CLI. Thanks for the MR @Kasperg

contrib.social Blog FAQ Discussions
Production build 0.71.5 2024