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
The SSHExecutionService and LocalExecutionService use inconsistent behaviour with respect to
dealing with stdout and stderr (once its part of resultLines, once not)
dealing with wrapping commands in Bash
ExecutionResults should be able to handle stdout and stderr separately (but maybe optionally also intermingled, which is useful to keep the relative timing of output in both streams). Proper intermingled dealing, however, will still keep the lines from each separated!
Consider also whether asynchronous execution really makes sense, if much of the code is synchronous.
The text was updated successfully, but these errors were encountered:
The SSHExecutionService and LocalExecutionService use inconsistent behaviour with respect to
ExecutionResults should be able to handle stdout and stderr separately (but maybe optionally also intermingled, which is useful to keep the relative timing of output in both streams). Proper intermingled dealing, however, will still keep the lines from each separated!
Consider also whether asynchronous execution really makes sense, if much of the code is synchronous.
The text was updated successfully, but these errors were encountered: