node.add and node.name.publish are inconsistent.

[spasimir21]

• Version:

{ version: '0.43.2', repo: 7, commit: '' }

• Platform:

Linux <COMPUTER_NAME> 5.0.0-32-generic #34~18.04.2-Ubuntu SMP Thu Oct 10 10:36:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

• Subsystem:

name, files (regular)

Severity:

Question

Description:

I used js-ipfs in electron.
I can launch a node, but when I try to add a file it gives me an address every time,
but ipfs.io/ipfs/<BASE32_HASH> only resolves some of the time.
node.name.publish gives me an address every time, but
ipfs.io/ipns/<PEER_ID> doesn't resolve at all.
My question is:
Is there a time limit that blocks you from adding files
one after the other using different node.add calls,
or is it just a bug.
And about the name.publish:
Why does even a single publish not work.
Everything resolves if I try to cat or name.resolve in the same process.
Also I stop the node after the name.publish and add calls, but things don't work even before stopping the node.

[welcome]

Thank you for submitting your first issue to this repository! A maintainer will be here shortly to triage and review.
In the meantime, please double-check that you have provided all the necessary information to make this process easy! Any information that can help save additional round trips is useful! We currently aim to give initial feedback within two business days. If this does not happen, feel free to leave a comment.
Please keep an eye on how this issue will be labeled, as labels give an overview of priorities, assignments and additional actions requested by the maintainers:

• "Priority" labels will show how urgent this is for the team.
• "Status" labels will show if this is ready to be worked on, blocked, or in progress.
• "Need" labels will indicate if additional input or analysis is required.

Finally, remember to use https://discuss.ipfs.io if you just need general support.

[bertrandfalguiere]

Puplished CID or IPNS records take some time to propagate through the network. The IPFS nodes maintained by ipfs.io need some time to learn about your recent publications. Wait a bit and retry to fetch via ipfs.io

[spasimir21]

Also the library itself can't fetch it from a new process.

[spasimir21]

I just tried the old addresses from about an hour ago and they still don't work.

[achingbrain]

Also the library itself can't fetch it from a new process.

I assume this means you're running two nodes at the same time - can you verify that both nodes have dialled each other?

You should be able to see the address of the other node in the peer list with:

$ jsipfs swarm list

[spasimir21]

node.add seems to have worked and is accessible through ipfs.io/ipfs but I still can't get node.name.publish to work

[jacobheun]

IPNS working properly is blocked by the DHT here, as there isn't an effective route with the current pubsub system without enough nodes on the network also running it (which is not currently the case).

[achingbrain]

js-ipfs is being deprecated in favor of Helia. You can #4336 and read the migration guide.

Publishing IPNS records to the DHT has been supported for a while so please try using @helia/ipns with the DHT routings.

It does depend on the publishing node having good network connections and being able to dial remote peers so it's worth using the onProgress option to see what's happening under the hood.

Please open further issues against the @helia/ipns repo if you continue to have probems.