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
I think this is sort of a duplicate of #212 so I'm going to close this out here. Currently using stdin with exec is just broken with the websockets API in Kubernetes. We need a solution to be released upstream in Kubernetes.
@jacobtomlinson Is it possible to have the "less broken" behavior in the meantime? Eg. what the official library does -- can pass stdin, but it can't be closed client-side.
I'm currently using the official library with a workaround -- closing the input server-side by piping the input through /usr/bin/sed '/\\x0/Q' and sending a null byte at the end, which works for my use case since I send only text.
I'd be happy to make it possible to opt into using stdin, but given that users will undoubtedly fall into the trap of trying and failing to close the stream on the client side I'd like to think of a way for users to explicitly opting into this.
Which project are you reporting a bug for?
kr8s
What happened?
I tried using
pod.exec
withstdin
, but got an error messageAttributeError: 'AsyncWebSocketSession' object has no attribute 'protocol'
from this line:kr8s/kr8s/_exec.py
Line 73 in 3d7ac19
protocol
should besubprotocol
in the error message.It seems like the only passed protocol is the v4 one (
kr8s/kr8s/_exec.py
Line 21 in 3d7ac19
kr8s/kr8s/tests/test_objects.py
Line 876 in 3d7ac19
I saw no tracking issue, so I am reporting this even though the underlying issue seems to be already known.
Anything else?
No response
The text was updated successfully, but these errors were encountered: