mirror of
https://github.com/kubernetes/client-go.git
synced 2025-06-29 16:36:54 +00:00
804ee8c42e
Normal execution always started to trigger this after adding more logging in
the E2E framework's exec_util.go:
I0506 21:23:56.781188 6341 exec_util.go:201] unexpected error trying to use websockets for pod exec: <nil>
That the "should fall back" implementation gets called when there is no error
and thus no reason to even consider falling back is odd. Now the execute
implementation checks for nil first.
This is the same approach taken also in the portforward code:
|
||
|---|---|---|
| .. | ||
| doc.go | ||
| errorstream.go | ||
| fallback_test.go | ||
| fallback.go | ||
| OWNERS | ||
| reader.go | ||
| remotecommand.go | ||
| resize.go | ||
| spdy_test.go | ||
| spdy.go | ||
| v1.go | ||
| v2_test.go | ||
| v2.go | ||
| v3.go | ||
| v4_test.go | ||
| v4.go | ||
| v5.go | ||
| websocket_test.go | ||
| websocket.go | ||