Receive Timeout #12
Open
Receive Timeout #12
Conversation
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
fred314159265
force-pushed
the
receive_timeout
branch
from
b4f65ac to
9260ed3
Compare
Signed-off-by: fred314159265 <[email protected]>
fred314159265
force-pushed
the
receive_timeout
branch
from
9260ed3 to
3e92556
Compare
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.
Added the ability to specify the receive timeout, I have only added the option to the
*_with_opts()methods, so the API remains the same for theopen()andopen_if()methods, but it is a breaking change for those using the*_with_opts()methods.I have tested this with a
vcanand it returns in around the amount of time according to what the timeout is set to.