If drush_backend_parse_output() returns a string, it means the command could have run successfully.

[jonpugh]

I'm running into a very strange issue with a site hosted on Aegir (Running Drush 8). It only happens with a Drupal 8 platform based on the standard drupal composer project, which itself includes Drush.

In aegir, the drush provision-verify command uses drush_invoke_process() to run drush provision-save. When I do this on the Drupal 8 platform, drush_invoke_process() throws the error "The command could not be executed successfully".

If I remove the vendor/drush/drush folder from the Drupal 8 platform, the command works as expected!

What happens is that drush_backend_parse_output() returns the output of the drush provision-verify command as a string when it bootstraps the Drupal8/drush9 platform.

I have no idea how this could be happening, but I figured _drush_backend_invoke() should handle that string instead of an array.

[jonpugh]

Some others who have seen the issue:

https://www.drupal.org/node/2821807
https://www.drupal.org/project/provision/issues/2796555

[weitzman]

I'd love to do some root cause analysis here. drush_invoke_process() is supposed to return an array.

[greg-1-anderson]

Maybe the remote call is getting switched to interactive mode instead of backend mode?

I second that we should identify the root cause before just fixing the symptom. It could be that we proceed as suggested here, but we should know why first, lest we mask some other problem.

[weitzman]

I wonder if this is another instance of #3127

[greg-1-anderson]

I think that the problem here is that Drush is going through the wrong code path here. I don't think this function should be fixed like this, because we shouldn't be here unless the remote end was asked to produce backend json output.

[weitzman]

no activity