websocket: [BUG] 1.5.1 uses log.Printf
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
Commit 666c197fc9157896b57515c3a3326c3f8c8319fe is a huge commit with no useful log message, and I keep finding new issues with it.
One of the issues is that it included a bunch of error handling using log.Printf. gorilla/websocket is a generally useful library, and it should not be making any assumptions about my application’s logging infrastructure; using log.Printf for logging is a clear violation of this basic principle.
Please revert commit 666c197fc9157896b57515c3a3326c3f8c8319fe.
Expected Behavior
A low-lever library should not be doing logging on behalf of the application.
Steps To Reproduce
No response
Anything else?
No response
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 6
- Comments: 19 (10 by maintainers)
Commits related to this issue
- Reverts to v1.5.0 This commit reverts the changes back till https://github.com/gorilla/websocket/commit/8983b963247d87e6caf0e3b72db2539590f1b2c6. And inherits the README.md changes of https://github.... — committed to apoorvajagtap/gorilla-websocket by apoorvajagtap 2 years ago
- Reverts to v1.5.0 This commit reverts the changes back till https://github.com/gorilla/websocket/commit/8983b963247d87e6caf0e3b72db2539590f1b2c6. And inherits the README.md changes of https://github.... — committed to gorilla/websocket by apoorvajagtap 2 years ago
- go mod: websocket: go back to v1.5.0 For the unfortunate chaos of the current upstream project status. Ref https://github.com/gorilla/websocket/issues/880 — committed to yousong/socketio-go by yousong 2 years ago
- chore: Bump gorilla/websocket to 1.5.3 This change has some history. Originally there was v1.5.0, then the project stalled and eventually the repo got archived. Some new maintainers stepped up and re... — committed to libp2p/go-libp2p by MarcoPolo 2 years ago
- chore: Bump gorilla/websocket to 1.5.3 This change has some history. Originally there was v1.5.0, then the project stalled and eventually the repo got archived. Some new maintainers stepped up and re... — committed to libp2p/go-libp2p by MarcoPolo 2 years ago
- chore: Bump gorilla/websocket to 1.5.3 This change has some history. Originally there was v1.5.0, then the project stalled and eventually the repo got archived. Some new maintainers stepped up and re... — committed to libp2p/go-libp2p by MarcoPolo 2 years ago
- Release v0.35.2 (#2863) * pstoremanager: fix connectedness check * Close quic conns when wrapping conn fails * Add a transport level test to ensure we close conns after rejecting them by the rc... — committed to libp2p/go-libp2p by MarcoPolo 2 years ago
@AlexVulaj, the problem is that since 666c197 is so large and undocumented, it is impossible to review.
If you want us to trust gorilla/websocket again, you need to revert 666c197, and then resubmit the useful changes in manageable units with proper commit messages. Leaving the commit in and then playing whack-a-mole with the issues it introduced is not going to produce sofftware we can depend on.
@AlexVulaj This is not a mere desire. There is simply no way to review that commit, and hence there is no way to convince ourselves that no erroneous or even malicious code has been snuck into Gorilla websocket.
It is simply not possible for us to trust this branch of Gorilla Websocket as long as this commit is not reverted and the features submitted again in byte-sized chunks with proper commit messages.
The problematic commit has been in the repository for almost eight months now, and has still not been reverted. At this point, I find it very difficult to trust the new maintainer of gorilla/websocket, and am considering forking the repository from the last trustworthy version.
I believe that the proper way to proceed would be to revert said commit, and then resubmit the useful parts with proper commit messages. If that is not done, then somebody will need to fork the package.
Trust went out the window shortly after the project was unarchived.
You do not lose changes by removing broken code, that’s a terrible thing to even suggest. You are, however, losing users because you refuse to address this problem in a timely manner.
Good luck to all!
This is open source, feel free open up a set of PRs that bring your trust back folks. The contributors here took an archived project and added support, which is very generous of them. It’s part of the open source community to support these worries - even when mistakes were made previously.
Hey all - one of our maintainers submitted this PR to hopefully undo the logging that was added causing all of the extra noise. Hoping to get that pushed through soon.