Skip to content
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(websocket): Continue waiting for TCP connection to be closed (IDFGH-11965) #495

Merged
merged 2 commits into from
Feb 8, 2024

Conversation

eht-datarespons
Copy link
Contributor

An issue was observed where the websocket client did not send WEBSOCKET_EVENT_CLOSED after server closed the websocket.

An alternative solution to fix the issue would be to remove the if instead. It could be more robust, but the existing comment seem to suggest that it was not the original intent.

Prevents an issue where WEBSOCKET_EVENT_CLOSED is not sent after
websocket is closed.
@CLAassistant
Copy link

CLAassistant commented Jan 23, 2024

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot changed the title fix(websocket): Continue waiting for TCP connection to be closed fix(websocket): Continue waiting for TCP connection to be closed (IDFGH-11965) Jan 23, 2024
@eht-datarespons
Copy link
Contributor Author

@david-cermak Are there any other changes i should make or is the current state of the pull request acceptable?

Copy link
Collaborator

@david-cermak david-cermak left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry for the delay. The change LGTM, thanks for posting this PR!

@david-cermak david-cermak merged commit 38a3631 into espressif:master Feb 8, 2024
54 checks passed
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.

5 participants