Skip to content

Feat/disconnect packet#2

Draft
falvia wants to merge 3 commits intomasterfrom
feat/disconnect-packet
Draft

Feat/disconnect packet#2
falvia wants to merge 3 commits intomasterfrom
feat/disconnect-packet

Conversation

@falvia
Copy link
Owner

@falvia falvia commented Feb 18, 2025

No description provided.

falvia and others added 3 commits February 12, 2025 17:39
Starting January 30th, 2025, GitHub Actions customers will no
longer be able to use v3. It is necessary to update to v4 to make
the workflows work.
As a consequence duplicated jobs are removed.

Signed-off-by: Flavia Caforio <[email protected]>
PR: workflows: fix update actions to v4

Closes IDFGH-14621

See merge request espressif/esp-mqtt!228
In the mqtt5 protocol the broker can disconnect the client with
a disconnect packet. This packet contains a reason value that can be
useful for certain applications in which it is important to know
the reason of disconnection.
While the client is connected is possible that a disconnect packet
is reaceived by the broker to force a disconnection. Before this
patch this approach causes a generic error on transport in case of
disconnection from the broker. If the packet is managed before getting
an error it is possible to save the reason code in the
disconnect_return_code variable in the error_handle, and dispatch
the disconnect event that can be managed by the application event
loop, that now can know the reason of disconnection from the broker.
Reset the variable in case of error.

Signed-off-by: Flavia Caforio <[email protected]>
@falvia falvia force-pushed the feat/disconnect-packet branch from e060903 to 470cb93 Compare February 18, 2025 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants