-
Notifications
You must be signed in to change notification settings - Fork 470
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
when listener handle a protocol, how to deal error? #176
Labels
kind/support
A question or request for support
status/deferred
Conscious decision to pause or backlog
Comments
With the new version of libp2p, using |
sounds good😀 |
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
Updates project config to publish typedocs
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
## [5.1.1](libp2p/js-libp2p-mdns@v5.1.0...v5.1.1) (2022-12-16) ### Documentation * publish typedocs ([libp2p#176](libp2p/js-libp2p-mdns#176)) ([7f3a41b](libp2p/js-libp2p-mdns@7f3a41b)) ### Trivial Changes * remove lockfile ([3c1b399](libp2p/js-libp2p-mdns@3c1b399))
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
Updates the interface and symbol return type
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
## [8.0.0](libp2p/js-libp2p-bootstrap@v7.0.1...v8.0.0) (2023-05-04) ### ⚠ BREAKING CHANGES * update @libp2p/interface-peer-discovery to 2.0.0 (libp2p#176) ### Dependencies * update @libp2p/interface-peer-discovery to 2.0.0 ([libp2p#176](libp2p/js-libp2p-bootstrap#176)) ([1954e75](libp2p/js-libp2p-bootstrap@1954e75))
maschad
added a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
Co-authored-by: Chad Nehemiah <[email protected]>
maschad
pushed a commit
to maschad/js-libp2p
that referenced
this issue
Jun 21, 2023
## [2.0.7](libp2p/js-libp2p-webrtc@v2.0.6...v2.0.7) (2023-06-07) ### Tests * actually run firefox tests on firefox ([libp2p#176](libp2p/js-libp2p-webrtc#176)) ([386a607](libp2p/js-libp2p-webrtc@386a607))
achingbrain
pushed a commit
that referenced
this issue
Jun 27, 2023
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
achingbrain
pushed a commit
that referenced
this issue
Jun 27, 2023
## [3.0.6](libp2p/js-libp2p-floodsub@v3.0.5...v3.0.6) (2022-09-07) ### Dependencies * **dev:** bump wherearewe from 1.0.2 to 2.0.1 ([#176](libp2p/js-libp2p-floodsub#176)) ([4897c65](libp2p/js-libp2p-floodsub@4897c65))
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
kind/support
A question or request for support
status/deferred
Conscious decision to pause or backlog
Type: Question
Severity: Low
Description:
sometimes, when a listener peer handle, it may get some errors, like dialer offline.
How to deal with these errors? use
console.log(error)
may be a bad idea. If use hangup, I can't get peerInfo from Connection.Steps to reproduce the error:
The text was updated successfully, but these errors were encountered: