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
(This is a smaller issue that continues from #9043, and a ipfs daemon equivalent to ipfs/ipfs-webui#1964)
Currently, ipfs daemon prints Swarm announcing for the initial, local multiaddresses. However, when using RelayClient, public multiaddresses aren't found until after Daemon is Ready and so are never reported.
Ideally, ipfs daemon's output should report additional Swarm announcing messages for multiaddresses found after it reports Daemon is ready.
The text was updated successfully, but these errors were encountered:
In this scenario, addresses are going to be influx.
Options:
Don't print out anything in ipfs daemson (stopping this may break sharness tests, which isn't good, but is the unfortunate state of the affairs)
Print everytime address changes (not a priority for maintainers currently)
Add extra log statement in ipfs daemon that addresses are in flux and use ipfs id. (cheapest way to give users a hint. This is where we'd want to invest.)
@Winterhuman : could you take on doing #3? It would be a small log statement to add.
Checklist
Description
(This is a smaller issue that continues from #9043, and a
ipfs daemon
equivalent to ipfs/ipfs-webui#1964)Currently,
ipfs daemon
printsSwarm announcing
for the initial, local multiaddresses. However, when usingRelayClient
, public multiaddresses aren't found until afterDaemon is Ready
and so are never reported.Ideally,
ipfs daemon
's output should report additionalSwarm announcing
messages for multiaddresses found after it reportsDaemon is ready
.The text was updated successfully, but these errors were encountered: