fix: clear collision state on reconnection with clean session#1019
Open
kiyov09 wants to merge 2 commits into
Open
fix: clear collision state on reconnection with clean session#1019kiyov09 wants to merge 2 commits into
kiyov09 wants to merge 2 commits into
Conversation
When reconnecting with a clean session (session_present=false), the collision state was not being cleared along with the pending packets. This could cause issues if a collision had occurred in the previous session, as the stale collision state would persist into the new session.
Author
|
Hi @giridher-art, pls take a look at my changes and let me know any additional changes I need to make. Thnx! |
Collaborator
|
hey @kiyov09 , we are currently working on a new architectural design for rumqttc . it contains all these changes and we may release it ASAP. |
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.
When reconnecting with a clean session (session_present=false), the collision state was not being cleared along with the pending packets. This could cause issues if a collision had occurred in the previous session, as the stale collision state would persist into the new session.
This is a fix for #1014
Type of change
Checklist:
cargo fmtCHANGELOG.mdif it's relevant to the users of the library. If it's not relevant mention why.