-
Notifications
You must be signed in to change notification settings - Fork 24
Add configurable limit on consecutive client response timeouts #166
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
Merged
Merged
Changes from all commits
Commits
Show all changes
10 commits
Select commit
Hold shift + click to select a range
1e505a9
add configuration type
jadamcrain 26fe8c3
integrate new feature that can fail sessions after a configurable num…
jadamcrain 573786f
fix off by one error
jadamcrain 41ad5ef
clarify that its response timeouts not just any request error
jadamcrain e7aa3ce
tweak docs
jadamcrain 1143a2f
test cases
jadamcrain 6fc07db
test the successful responses reset the counter to zero
jadamcrain 5adc166
anything other than a response timeout also resets the counter
jadamcrain 2eb8089
comments / formatting
jadamcrain 1e229e5
saturating add
jadamcrain File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The
max_timeoutsoption is hardcoded toNonefor the serial client, which disables the new consecutive timeout limit feature. The PR description and the addition ofSessionError::MaxTimeoutshandling for serial connections suggest this feature should be available for serial clients as well. To fix this, themax_timeoutsvalue should be configurable, likely by passingClientOptionstoSerialChannelTask::newsimilarly to how it's done for the TCP client.