We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The code has started printing debug messages to via log.Printf(). For example:
2023/09/19 09:27:23 websocket: discarding reader close error: io: read/write on closed pipe
It seems to have been introduced recently:
https://github.com/gorilla/websocket/blame/666c197fc9157896b57515c3a3326c3f8c8319fe/conn.go#L1025
No debug messages are printed to the console.
No response
The text was updated successfully, but these errors were encountered:
From the pull request notes, it seems like there were comments saying that writing to the application's stderr is unfriendly. I agree...
#840
Sorry, something went wrong.
Is there a way to get rid of those log messages? If it is not possible, how could I check if connection is closed before to call ReadMessage?
Regards
Successfully merging a pull request may close this issue.
Is there an existing issue for this?
Current Behavior
The code has started printing debug messages to via log.Printf(). For example:
2023/09/19 09:27:23 websocket: discarding reader close error: io: read/write on closed pipe
It seems to have been introduced recently:
https://github.com/gorilla/websocket/blame/666c197fc9157896b57515c3a3326c3f8c8319fe/conn.go#L1025
Expected Behavior
No debug messages are printed to the console.
Steps To Reproduce
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: