Routing-v1 gateway endpoint not returning enough information #10195
Labels
kind/bug
A bug in existing code (including security flaws)
status/blocked
Unable to be worked further until needs are met
Checklist
Installation method
ipfs-update or dist.ipfs.tech
Version
Config
No response
Description
When running against a node with
"ExposeRoutingAPI": true
and otherwise default routing I get less data than I can get by querying the underlying routing sources.Example:
However, when I query cid.contact (doesn't support streaming):
Note: Some peers like
QmUA9D3H7HeCYsirB3KmPSvZh3dNXMZas6Lwgr4fv1HTTp
and12D3KooWEkQFhSUc17MNC4gimbRYakSSCmDiQwMLhcvToh7bsXbN
are missing. These peers have return data like:Which seems to indicate that some less familiar schemas that might not be helpful to kubo itself (e.g. anything but
peer
andbitswap
) might be getting dropped. This is likely not what's intended when the API is used directly vs when it's been processed inside kubo for its use (i.e. internally kubo should of course drop the routing records it has no use for).Note: cid.contact may also have some bugs here in both emitting legacy record types and not handling metadata correctly.
The text was updated successfully, but these errors were encountered: