-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Regression: Drush 13.3 does not properly handle SIGQUIT signal #6137
Comments
The new way to launch Drush creates two additional shell processes besides the PHP. Also some people reported that Drush 13.3 is not working on Windows because of this change. |
@Chi-teck Could you try to run |
Yes, drush.php works correctly.
|
In the original PR I implemented it without exec, because the Composer Wrapper script also works this way. |
I'm proposing reverting the bash entrypoint in #6146. |
Use latest composer and Drush 13.3.1+ |
That apparently is caused by #6124.
Here is example of a simple long running Drush command
Start the above command and send SIGQUIT (Ctrl + \) to it.
Output Drush 13.2 (correct)
Output Drush 13.3 (wrong)
Note that in the last example "Done!" appears when Drush was already terminated. If a command is managed through some process manager, i.e. Supervisor, such behavior causes orphan processes.
The text was updated successfully, but these errors were encountered: