-
Notifications
You must be signed in to change notification settings - Fork 71
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
when the connection is broken, join() without Close() freezes for ten… #137
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
euank
pushed a commit
to euank/libngrok-go
that referenced
this pull request
May 28, 2024
Before, the following would not work as you would expect: ```go // # One terminal // $ ncat --recv-only -l 9090 // ngrok-go code fwd, err := sess.ListenAndForward( ctx, "127.0.0.1:9090", config.TCPEndpoint(), ) // fwd.URL() is 0.tcp.jp.ngrok.io:14517 for this example // another terminal // $ ncat --send-only 0.tcp.jp.ngrok.io 14517 < hello-world.txt ``` What we would expect from the above would be for the send side to send "hello world" and exit, and then the recv side to print "hello world" and also exit. This is what happens if you do `ncat --send-only localhost 9090` instead of copying through the ngrok tcp tunnel. Before this change, when copying through ngrok the recv side would not exit because the 'Close' of the connection did not get propagated through the 'join'. I've also added a unit test showing this. Thank you to @abakum for originally noticing this issue and offering a fix over in ngrok#137. In the hopes of landing this more quickly, I've written a new version, derived from the internal ngrok agent's join code, which should thus be easier to review etc.
euank
pushed a commit
to euank/libngrok-go
that referenced
this pull request
May 28, 2024
Before, the following would not work as you would expect: ```go // # One terminal // $ ncat --recv-only -l 9090 // ngrok-go code fwd, err := sess.ListenAndForward( ctx, "127.0.0.1:9090", config.TCPEndpoint(), ) // fwd.URL() is 0.tcp.jp.ngrok.io:14517 for this example // another terminal // $ ncat --send-only 0.tcp.jp.ngrok.io 14517 < hello-world.txt ``` What we would expect from the above would be for the send side to send "hello world" and exit, and then the recv side to print "hello world" and also exit. This is what happens if you do `ncat --send-only localhost 9090` instead of copying through the ngrok tcp tunnel. Before this change, when copying through ngrok the recv side would not exit because the 'Close' of the connection did not get propagated through the 'join'. I've also added a unit test showing this. Thank you to @abakum for originally noticing this issue and offering a fix over in ngrok#137. In the hopes of landing this more quickly, I've written a new version, derived from the internal ngrok agent's join code, which should thus be easier to review etc. To try and give credit correctly, I've maintained the original commits from ngrok#137 as well.
euank
added a commit
to euank/libngrok-go
that referenced
this pull request
May 28, 2024
Before, the following would not work as you would expect: ```go // # One terminal // $ ncat --recv-only -l 9090 // ngrok-go code fwd, err := sess.ListenAndForward( ctx, "127.0.0.1:9090", config.TCPEndpoint(), ) // fwd.URL() is 0.tcp.jp.ngrok.io:14517 for this example // another terminal // $ ncat --send-only 0.tcp.jp.ngrok.io 14517 < hello-world.txt ``` What we would expect from the above would be for the send side to send "hello world" and exit, and then the recv side to print "hello world" and also exit. This is what happens if you do `ncat --send-only localhost 9090` instead of copying through the ngrok tcp tunnel. Before this change, when copying through ngrok the recv side would not exit because the 'Close' of the connection did not get propagated through the 'join'. I've also added a unit test showing this. Thank you to @abakum for originally noticing this issue and offering a fix over in ngrok#137. In the hopes of landing this more quickly, I've written a new version, derived from the internal ngrok agent's join code, which should thus be easier to review etc. To try and give credit correctly, I've maintained the original commits from ngrok#137 as well.
euank
added a commit
that referenced
this pull request
May 29, 2024
Before, the following would not work as you would expect: ```go // # One terminal // $ ncat --recv-only -l 9090 // ngrok-go code fwd, err := sess.ListenAndForward( ctx, "127.0.0.1:9090", config.TCPEndpoint(), ) // fwd.URL() is 0.tcp.jp.ngrok.io:14517 for this example // another terminal // $ ncat --send-only 0.tcp.jp.ngrok.io 14517 < hello-world.txt ``` What we would expect from the above would be for the send side to send "hello world" and exit, and then the recv side to print "hello world" and also exit. This is what happens if you do `ncat --send-only localhost 9090` instead of copying through the ngrok tcp tunnel. Before this change, when copying through ngrok the recv side would not exit because the 'Close' of the connection did not get propagated through the 'join'. I've also added a unit test showing this. Thank you to @abakum for originally noticing this issue and offering a fix over in #137. In the hopes of landing this more quickly, I've written a new version, derived from the internal ngrok agent's join code, which should thus be easier to review etc. To try and give credit correctly, I've maintained the original commits from #137 as well.
I carried forward and merged an equivalent change over in #163, closing this one as resolved via that PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
…s of seconds