-
Notifications
You must be signed in to change notification settings - Fork 17.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
Stuck Hijack() on net.Conn compatible I/O server rnet/http.(*conn).hijackLocked #48167
Comments
Terminating the process with Stack trace$ ./go-http-hijack-bug ^\SIGQUIT: quit PC=0x7fff2038ecde m=0 sigcode=0 And in particular this struck goroutine:
|
Your net.Conn implementation has to actually satisfy the behavior described for the interface's methods, not just have stub methods, in particular see #20963 (comment) |
After much hacking I actually did manage to do exactly that (very ugly though) and ran into another issue resulting in a |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
The follow code (re-pasted here for posterity) exhibits a bug? very similar to this issue that was discussed and closed with no fixes/changes? to the Go std library some years ago.
Compiling and running this:
docker
client with a simple:DOCKER_HOST=ssh://localhost:2222 docker run -i --rm alpine echo Hello World
For clarity:
And connect a Docker CLI client:
What did you expect to see?
I expect to see:
from running the Docker CLI client with the above sample.
This should also in turn start and attach to the created container. You can see the container has in fact been created in a "created" state:
What did you see instead?
Observe that the Docker CLI client above "hangs" with the expected output of "Hello World" not shown and the container is never run.
The text was updated successfully, but these errors were encountered: