bug: dht/findPeer - FINAL_PEER being returned with empty Addrs
#10117
Labels
kind/bug
A bug in existing code (including security flaws)
need/triage
Needs initial labeling and prioritization
Checklist
Installation method
ipfs-desktop
Version
Config
Description
Hey kubo-boxo-maintainers,
I’m looking into ipfs/js-kubo-rpc-client#176 and trying to figure out where functionality is documented regarding FINAL_PEER, QUERY_ERROR, and other response messages for a dht findPeer (i’m only seeing dht/query now) request.
if I query Kubo for a helia peer via curl, via both
curl -X POST "http://127.0.0.1:5001/api/v0/dht/findpeer?arg=$MY_PEER_ID"
curl -X POST "http://127.0.0.1:5001/api/v0/routing/findpeer?arg=$MY_PEER_ID"
I’m getting a response of
(Type 2 = FINAL_PEER), but since Addrs is empty, shouldn’t this return a QUERY_ERROR ?
Related
FINAL_PEER
being returned without diallable addresses js-kubo-rpc-client#176FIND_PEER
event libp2p/js-libp2p#1985The text was updated successfully, but these errors were encountered: