I was debugging why I could only ever connect to a limited number of unique peers, even though there are 175 with valid webtransport addresses, so i started logging peerIds with valid webtransport addresses that I could then search my console for other libp2p:* debug messages, and I discovered that one peer had the following "valid" address:
but then libp2p:dialer and libp2p:connection-manager throw the following error:
libp2p:dialer dial failed to 12D3KooWHCiY5NqNFu29BSyydye4ZfJtJNmti2GjmG8YUHdmudZ5 +0ms Error: unexpected component in multiaddr: 290 p2p-circuit
at parts.reduce.url (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:66128:23)
at Array.reduce (<anonymous>)
at parseMultiaddr (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:66071:51)
at WebTransportTransport.dial (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:66172:49)
at DefaultTransportManager.dial (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:103241:36)
at DialRequest.dialAction (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:99263:59)
at http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:98942:39
at async Promise.any (index 0)
at async DialRequest.run (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:98928:20)
at async DefaultDialer.dial (http://localhost:3000/vendors-node_modules_file-type_core_js-node_modules_chainsafe_libp2p-yamux_dist_src_index_js--def13e.bundle.js:99126:32)
I am not familiar with p2p-circuit nor if this is actually a valid address, but it seems valid, and we should probably add support here.
I'm working on https://github.com/ipfs-shipyard/helia-service-worker-gateway.
I was debugging why I could only ever connect to a limited number of unique peers, even though there are 175 with valid webtransport addresses, so i started logging peerIds with valid webtransport addresses that I could then search my console for other libp2p:* debug messages, and I discovered that one peer had the following "valid" address:
/ip4/108.62.0.103/udp/4001/quic-v1/webtransport/certhash/uEiD4910kDDyQfhYln8G5KDQmp71tmWFzS35GU0C2BI6Gzw/certhash/uEiABwkoVynkcX6U02j8snwCMVv2HP1mA6zc0iJtxYxSL4A/p2p/12D3KooWStaeh9g1m4fqsGSKdNGDHtifEBd4NhSRMLfBNoN8YRhn/p2p-circuit
libp2p:dialer shows the following addresses for this peer:
but then
libp2p:dialer
andlibp2p:connection-manager
throw the following error:I am not familiar with p2p-circuit nor if this is actually a valid address, but it seems valid, and we should probably add support here.
related