-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
UPSTREAM: 13322: Various exec fixes #4535
Conversation
[test] |
transitive LGTM from @smarterclayton upstream |
Extended is currently borked. Care to merge instead? |
yeah, [merge] |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/4791/) |
Evaluated for origin test up to f4ff7c8 |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_requests_origin/4791/) (Image: devenv-fedora_2289) |
Evaluated for origin merge up to f4ff7c8 |
I can still trigger a hang even with this PR. This is without a TTY stdin. (i get this in the server but it's not when I CTRL+C the command)
|
What's the exact command and sequence of operations? |
My branch, rsync -avvv -e "oc rsh" file pod:/dir On Sep 5, 2015, at 1:43 PM, Jordan Liggitt notifications@github.com wrote: What's the exact command and sequence of operations? — |
Upstream PR: kubernetes/kubernetes#13322
Includes dockerclient fixes from #4467 (cc @csrwng)
Fixes BZ 1255502
Fixes #4239
Fixes #4445