Added a receive flush timeout just prior to launching the next poll when#65
Open
wz2b wants to merge 1 commit intogoburrow:masterfrom
Open
Added a receive flush timeout just prior to launching the next poll when#65wz2b wants to merge 1 commit intogoburrow:masterfrom
wz2b wants to merge 1 commit intogoburrow:masterfrom
Conversation
using a TCP connection. Without this, a slow response can cause transaction ID mismatches for the life of this TCP connection (it never recovers). This occurs when a remote device does answer, but it answers too slowly. The request has already timed out, and when the next request is launched the previous response is read (rather than the new one) causing this error.
|
hi,i think you should change the SetReadDeadline(time.now) to SetReadDeadline(time.now().add(time.millisecod*1)) |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
using a TCP connection. Without this, a slow response can cause
transaction ID mismatches for the life of this TCP connection (it
never recovers). This occurs when a remote device does answer, but
it answers too slowly. The request has already timed out, and when
the next request is launched the previous response is read (rather
than the new one) causing this error.