fix(websocket): remove redundant timeout check in client task loop #935
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.
Remove dead code from WEBSOCKET_STATE_CONNECTED case that checked
read_select == 0. This condition is already properly handled by the
poll/receive logic outside the switch statement.
Note
Removes a redundant
read_select == 0check inWEBSOCKET_STATE_CONNECTEDand centralizes read poll timeout logging in the post-poll branch.components/esp_websocket_client/esp_websocket_client.c):read_select == 0handling insideWEBSOCKET_STATE_CONNECTED.esp_transport_poll_read()to log read poll timeouts (ESP_LOGV).Written by Cursor Bugbot for commit 1e83bee. This will update automatically on new commits. Configure here.