You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently if you are using callbacks, commands are blocking other commands from execution.
It would be nice to have solution that does not have this problem.
I have done some research on this.
We could restructurize code a little bit. After starting an event we could send it to some watcher that checks status of events.
Inside runCommandInForeground function we could use start instead of run function from symfony process class and our watcher can check state using isRunning function from symfony process. After command stops we could run our callbacks and pass output as parameter using getOutput and getErrorOutput from symfony process class.
What is your opinion on this?
The text was updated successfully, but these errors were encountered:
Currently if you are using callbacks, commands are blocking other commands from execution.
It would be nice to have solution that does not have this problem.
I have done some research on this.
We could restructurize code a little bit. After starting an event we could send it to some watcher that checks status of events.
Inside
runCommandInForeground
function we could usestart
instead ofrun
function from symfony process class and our watcher can check state usingisRunning
function from symfony process. After command stops we could run our callbacks and pass output as parameter usinggetOutput
andgetErrorOutput
from symfony process class.What is your opinion on this?
The text was updated successfully, but these errors were encountered: