Fixes Incorrect Socket Timeout #28
Open
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
|
This fixed my issues! Thank you. |
|
I confirm, removing / 1000 is fundamental or running a ssh comman will rarely work. I installed via pod a few days ago, the bug is still there. The easiest is to correct it straight in XCode, for now. |
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.
self.timeoutis already converted to seconds so the extra/1000changes the default 10 second timeout to 0.01 seconds. That's long enough that 1 out of every 3 or 4 attempts will connect correctly but the rest fail with the output:This should resolve #24.