You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am running the latest kubo version or have an issue updating.
Installation method
ipfs-update or dist.ipfs.tech
Version
0.27.0
Config
lmk if you really need it
Description
i'm working on gateway conformance tests in @helia/verified-fetch and ran into issues with resolving IPFS_NS_MAP peerIds when calling the ${kuboGateway}/api/v0/resolve/${peerId} endpoint:
basic-server:dns response from Kubo:
'{"Path":"/ipfs/k51qzi5uqu5dilgf7gorsh9vcqqq4myo6jd4zmqkuy9pxyxi5fua3uf7axph4y"}\n'
There is a /n appended to the end, which makes parsing the response as JSON annoying. i.e. you can't just do:
gammazero
added
P2
Medium: Good to have, but can wait until someone steps up
and removed
need/triage
Needs initial labeling and prioritization
labels
Dec 10, 2024
Checklist
Installation method
ipfs-update or dist.ipfs.tech
Version
Config
lmk if you really need it
Description
i'm working on gateway conformance tests in @helia/verified-fetch and ran into issues with resolving IPFS_NS_MAP peerIds when calling the
${kuboGateway}/api/v0/resolve/${peerId}
endpoint:There is a
/n
appended to the end, which makes parsing the response as JSON annoying. i.e. you can't just do:and instead need to do:
const peerJson = JSON.parse(await peerResponse.text()).trim())
The text was updated successfully, but these errors were encountered: