-
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Drall 2.x and 3.x cannot catch some Drush output #71
Comments
This is likely related to the fact that drush writes to stderr. You would need to catch both the standard out and the standard error. :) |
I took a look into this today. It appears you are using the amp library to run the processes (versus Symfony). Amp separates the output streams into stdout and stderr. Symfony, on the other hand, provides you with a stream and you can get the type of data. In your example, you create an amp process. Perhaps the amp library should be able to provide a stream of both like Symfony does or maybe there is a better way of muxing the data together? It would be weird to print stdout then stderr since they are timed data and could interweave. |
Thanks for the insight. I will do some research in the first week of May and the worst of cases, I'll request AMP maintainers to help. |
I was reading a bit about this and it turns out that Drush writes all log messages to
Reference: drush-ops/drush#707 |
I've made a commit that fixes this issue and catches STDERR output correctly. However, there seems to be an irrelevant issue where |
Catch both STDOUT and STDERR output; fixes #71
The problem
drall ex drush cr
[success] Cache rebuild complete.
message generated by Drush.The text was updated successfully, but these errors were encountered: