Patrick Ohly 804ee8c42e client-go remotecommand: avoid "unexpected error" log when there is no error ... 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: b35c5c0a30/staging/src/k8s.io/client-go/tools/portforward/fallback_dialer.go (L52) Kubernetes-commit: 35870c480d64a8ae35c0e5839cc40b0115b7328a		2025-05-07 14:51:18 +02:00
..
auth
cache	chore: Add VeryShortWatchError typed error	2025-04-15 11:48:57 -07:00
clientcmd	Deprecate kubeconfig's preference field in favor of kuberc	2025-05-13 13:39:13 +02:00
events	events: ensure the name is valid	2025-02-20 09:13:56 +00:00
internal/events
leaderelection	Add LeaseCandidate v1beta1	2025-02-19 21:43:35 +00:00
metrics
pager
portforward	Fix test cases that may potentially cause a panic.	2025-03-11 17:41:37 +08:00
record	events: ensure the name is valid	2025-02-20 09:13:56 +00:00
reference
remotecommand	client-go remotecommand: avoid "unexpected error" log when there is no error	2025-05-07 14:51:18 +02:00
watch