-
-
Notifications
You must be signed in to change notification settings - Fork 3.2k
"ipfs stats dht" doesn't work with Routing.Type=custom #9482
Copy link
Copy link
Open
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)topic/commandsTopic commandsTopic commandstopic/dhtTopic dhtTopic dht
Description
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importantkind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)topic/commandsTopic commandsTopic commandstopic/dhtTopic dhtTopic dht
Checklist
Installation method
built from source
Version
Config
...
Description
When using custom routing, for example using the config detailed in the v0.16 release notes, the
ipfs stats dhtcommand returnError: routing service is not a DHT, even though there is a DHT in there.I understand the relative complexity of searching for a DHT in a custom routing pipeline and the possible edge cases, but it would be nice if that command would work in the (very common) case where there is exactly one DHT. Not only DHT stats are obviously useful, but my understanding is that it's also the only way to figure out if the accelerated DHT is ready to publish.