-
Notifications
You must be signed in to change notification settings - Fork 3
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
fix(uat): bypass send DISCONNECT on dead connection in SDK client #376
Merged
MikeDombo
merged 2 commits into
uat-dev
from
GGMQ-272-different-behaviors-between-mqtt-3-5
Jul 24, 2023
Merged
fix(uat): bypass send DISCONNECT on dead connection in SDK client #376
MikeDombo
merged 2 commits into
uat-dev
from
GGMQ-272-different-behaviors-between-mqtt-3-5
Jul 24, 2023
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
MikeDombo
approved these changes
Jul 24, 2023
Unit Tests Coverage Report
Minimum allowed coverage is Generated by 🐒 cobertura-action against f29abe4 |
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.
Issue #, if available:
Different behaviors between mqtt3 and mqtt5 when shutting down closed connection
Description of changes:
Why is this change necessary:
SDK MQTT v3 client throw an exception while try to call disconnect() on connection dropped by broker.
The same time SDK MQTT v5 client pass as usual.
To avoid control confuse we need to unify client behavior despite of MQTT version.
How was this change tested:
Manually by terminate local mosquitto broker after client has been connected
MQTT v3.1.1
Control:
SDK client:
MQTT v5
Control:
Client
Any additional information or context required to review the change:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.