Review logging across WebSocket implementation#397
Merged
mathieucarbou merged 1 commit intomainfrom Mar 9, 2026
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR standardizes and expands verbose logging across the WebSocket send/ack/data paths to improve traceability (server URL, client ID, opcode, and queue state).
Changes:
- Refactors multiple log messages to use a consistent prefix format (e.g.,
[%s][id],SEND[...],DATA ...). - Adds start/end and state-transition logs for ACK processing and queue operations.
- Adds/logs additional lifecycle events (close, error, timeout, disconnect) and a cleanup log.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
b164a83 to
ea24c63
Compare
me-no-dev
approved these changes
Mar 9, 2026
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
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.
This PR adds some verbose logging to the WebSocket implementation on top of the existing one (which as been reviewed) in order to help users debug.
Example when using
USE_ESP_IDF_LOG:Output example