-
-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
IPNS could not resolve name through Gateway #9927
Comments
@Man-Jain are you failing to resolve on the same machine that published the record that works fine on ipfs.io, or a different one? |
Yes, failing to resolve on the same machine from which the record was published. It's also not able to resolve any other IPNS record not published from that node. |
There are two bugs here:
So I tested this behaviour (fetching my own record), I can see my own node is reaching out to the DHT |
I will likely look (and possibly cleanup) |
I found out 3 bugs that prevents IPNS from working quickly right now. The DHT quorum is between 200~400ms for me, this is the expected IPNS resolution speed and would be if we were not artificially slowing it down. |
Triage notes:
|
2023-07-06 conversation: in addition to doing the fix and test, we need to create metrics and have it show up in Thunderdome. @lidel will create the followup issue for splitting out metrics between dnslink and ipns and making sure it shows up in Thunderdome. |
That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. Fixes: #9927
That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. This also include other error handling bug fixes inside `go-libp2p-routing-helpers`. Fixes: #9927
That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. This also include other error handling bug fixes inside `go-libp2p-routing-helpers`. Fixes: #9927
That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. This also include other error handling bug fixes inside `go-libp2p-routing-helpers`. Fixes: #9927
That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. This also include other error handling bug fixes inside `go-libp2p-routing-helpers`. Fixes: #9927
* fix: mark ipns pubsub router DoNotWaitForSearchValue That means if the DHT has finished searching and no one responded over pubsub *yet*, we will not spend 1 minute searching for no reason. This also include other error handling bug fixes inside `go-libp2p-routing-helpers`. Fixes: #9927 * routing: bring back the old IPNS behaviour Stop making this configurable let everything race like it used to do.
Checklist
Installation method
ipfs-desktop
Version
Config
Description
I have an ipfs gateway running on a kuberentes, all ports exposed and appendAddress has the ip and random port(4001) of the ipfs gateway node, usePubsub is true and on running ipfs name resolve & through ipfs.io i’m able to resolve IPNS hash.
But I have not been able to resolve IPNS hash through the gateway on port 8080.
I keep getting the error could not resolve name.
The text was updated successfully, but these errors were encountered: