Skip to content
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

it may be that the port the remote process wants to listen on is taken #3

Closed
haarcuba opened this issue May 8, 2018 · 0 comments
Closed
Assignees
Labels

Comments

@haarcuba
Copy link
Owner

haarcuba commented May 8, 2018

suggest that the remote process listen first, and then send data back to the local side with the correct port number. This requires the local process to have a listening socket and wait for info to come back, which introduces the issue - what if info never comes back? etc.

@haarcuba haarcuba added the bug label May 8, 2018
@haarcuba haarcuba self-assigned this May 8, 2018
haarcuba added a commit that referenced this issue Jun 27, 2018
haarcuba added a commit that referenced this issue Jul 2, 2018
haarcuba added a commit that referenced this issue Jul 3, 2018
haarcuba added a commit that referenced this issue Jul 4, 2018
this is a nice-to-have sort of feature. It will usually work, but only
if the remote closer is Python 3, and if the remote process did not die too soon

closes issue #3
haarcuba added a commit that referenced this issue Jul 5, 2018
this is a nice-to-have sort of feature. It will usually work, but only
if the remote closer is Python 3, and if the remote process did not die too soon
@haarcuba haarcuba closed this as completed Jul 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant