Florian Weber

It is considered as best practice to ship drush commands with your project. Clone drush_language to sites/default/drush/commands or drush/commands in your Drupal repo.

@iona5 @stephen What it necessary to get it done?

Please verify your SSH connection settings. Take a look at https://github.com/geerlingguy/mac-dev-playbook/issues/93 for more information.

@moll The bug appear only if you deploy in a complete cold env. No current, release, shared folder etc.

Related to https://github.com/drush-ops/drush-launcher/issues/47 ?

@weitzman Do you have any idea whats causing this? @ixisandyr @schady4 @dougmorin Could you add the --debug oder --verbose flag to the drush commands and post the full error log?...

We switched from system to proc_open in 0.6.x. https://github.com/drush-ops/drush-launcher/pull/44 I always setup the proper drush-script path in my site aliases. Makes debugging easier and it removes the requirement to have...

@back-2-95 Can you run updb with ``--debug -vvv``? Thanks. Or maybe its related to xdebug-handler. Try to run it with ``DRUSH_ALLOW_XDEBUG=1`` in front of the command.

The install instructions on https://github.com/drush-ops/drush-launcher/blob/master/README.md#installation---phar contain some information for Windows users (Step 4). Have you looked at these?

https://github.com/composer/xdebug-handler/issues/114