-
Notifications
You must be signed in to change notification settings - Fork 11
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: catch listen error #34
Conversation
cc @achingbrain |
Codecov Report
@@ Coverage Diff @@
## master #34 +/- ##
==========================================
+ Coverage 96.02% 96.07% +0.04%
==========================================
Files 22 22
Lines 957 967 +10
Branches 158 160 +2
==========================================
+ Hits 919 929 +10
Misses 38 38
Flags with carried forward coverage won't be shown. Click here to find out more.
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
The reason this is failing is because the websocket server forwards any error events emitted by the underlying http(s) server when it's passed as an option. If you stick a We probably want to be a bit smarter about error handling than that though. We could update the internal |
@achingbrain It works now. Hope I didn't do anything stupid 😅 |
Co-authored-by: Alex Potsides <alex@achingbrain.net>
## [5.0.6](v5.0.5...v5.0.6) (2022-12-08) ### Bug Fixes * catch listen error ([#34](#34)) ([7a96e45](7a96e45))
🎉 This PR is included in version 5.0.6 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This should fix it but for whatever reason it's not working. Please help.
Related to: libp2p/js-libp2p-websockets#184 (comment)