correct 0.38.0 changelog session_present=0 note to match shipped behavior - #120
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The deferred-ack
Addedentry for mqtt5 0.38.0 (written 2026-07-20 for core PR #117) ended with a "Known limitation" stating that a reconnect withsession_present = 0does not reconcile the client's in-memory de-duplication state. The #118 hardening (955953d) implemented exactly that reconciliation:on_successful_connectnow clears inbound QoS 2 dedup state (clear_all_inbound_state) and re-sends deferred-ack subscriptions on a lost session. This corrects the note to match the shipped behavior before tagging v0.38.0.