-
Notifications
You must be signed in to change notification settings - Fork 440
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
Websocket connection error #245
Comments
It would be good to wrap the code in With the variety of transports libp2p has, we should have them each conform to not throwing errors and instead returning them via callbacks to make the dial handler code in libp2p-switch more uniform. I've created an issue, libp2p/js-libp2p-websockets#77, to track this. If you're up for submitting a PR that would be much appreciated! |
Closing as this is specific to the websocket transport - please see libp2p/js-libp2p-websockets#77 to continue. |
* deps(dev): bump aegir from 38.1.8 to 39.0.9 Bumps [aegir](https://github.com/ipfs/aegir) from 38.1.8 to 39.0.9. - [Release notes](https://github.com/ipfs/aegir/releases) - [Changelog](https://github.com/ipfs/aegir/blob/master/CHANGELOG.md) - [Commits](ipfs/aegir@v38.1.8...v39.0.9) --- updated-dependencies: - dependency-name: aegir dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> * chore: fix linting --------- Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: achingbrain <alex@achingbrain.net>
## [6.0.3](libp2p/js-libp2p-websockets@v6.0.2...v6.0.3) (2023-06-06) ### Dependencies * **dev:** bump @libp2p/interface-mocks from 11.0.3 to 12.0.1 ([libp2p#241](libp2p/js-libp2p-websockets#241)) ([f956836](libp2p/js-libp2p-websockets@f956836)) * **dev:** bump aegir from 38.1.8 to 39.0.9 ([libp2p#245](libp2p/js-libp2p-websockets#245)) ([4a35f6b](libp2p/js-libp2p-websockets@4a35f6b))
Type: Question
Severity: Low
Description: When a node is disconnected from the internet, when internet comes back, it shows the below error. Obviously because it can't open a webscoket connection with another node. But my question is, can we catch it?
The text was updated successfully, but these errors were encountered: