TImeout on initial request fixed #70
Merged
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
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.
Just after connection the
McuMgrBleTransportrequests McuMgr parameters from the device. This request may succeed, may fail (rc=8), or may time out (1 sec). After the timeout the library would send another requests and, as it would be the first one done using thesendmethod, it would get sequence number 0. However, sometimes the response for the McuMgr params is received after 1 sec and, as it had also sequence set to 1, the library matched it with a wrong request and operation would fail. This PR ensures that the initial request has a different sequence number.