-
Notifications
You must be signed in to change notification settings - Fork 926
-
Notifications
You must be signed in to change notification settings - Fork 926
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
Executing cf ssh
over CliConnection.CliCommand
mixes stdout
and stderr
#1074
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/140310579 The labels on this github issue will be updated when the story is started. |
I hear from my anchor that architecturally the plugin code dumps everything it captures in stdout and stderr, it does not separate the two, and it would be a bit of work to separate stderr and stdout. And that could potentially be a breaking change for existing plugins. Regards, |
Here's a link to the epic for command refactoring: https://www.pivotaltracker.com/epic/show/3307969, , it's huge so will take a long time. |
We did an exploration around the behaviour you mentioned in this issue, and our findings do not match what you wrote. Can you take a look at the comments in https://www.pivotaltracker.com/story/show/141913339 and compare with your understanding? Cheers, |
I will run the tests again when I am back from vacations and update the issue accordingly. Cheers. |
Sorry, issue was between keyboard and chair :-) It is indeed the case that the |
When executing
cf ssh my_app -c '>&2 echo Ciao'
, "Ciao" is printed correctly tostderr
.When executing
cliConnection.CliCommand("ssh", "my_app", "-c", ">&2 echo Ciao")
, "Ciao" is printed tostdout
, which makes it fundamentally impossible to write good wrappers aroundcf ssh
for non-trivial commands.The text was updated successfully, but these errors were encountered: