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
It seems that adding a time.Sleep after the node starts tends to fix the issue, otherwise we might get a ErrNoAddresses from a node that tries to connect to a separate node that is started but not really available.
The text was updated successfully, but these errors were encountered:
Node Start just means the local node has started with all services up. It doesn't have to ensure the local node is connected to a peer. I think the ErrNoAddresses was occuring because of a dial to the peer(which hasn't probably finished identify).
I have gone through the Start of Wakunode2 and i don't see anything that is pending by the time we return apart from things that are supposed to happen async anyways.
Ah! i had missed these messages. Sorry for the delay.
Yeah, I went over it and the solution used by @qfrank in the end and i think this is a non issue. It seems that the test case relied in discv5 to connect to each other, but that can fail as seen in the status-go issue. I see the solution used does a dial to the node, and that for sure solved the problem since the nodes were connected to each other before the logic for the test was executed.
See for context.
status-im/status-go#4969 (comment)
It seems that adding a
time.Sleep
after the node starts tends to fix the issue, otherwise we might get aErrNoAddresses
from a node that tries to connect to a separate node that is started but not really available.The text was updated successfully, but these errors were encountered: