Open albrow opened 4 years ago
I have the same issue. Is this resolved?
@luandt-ibl the could not connect to peer
warning is expected. It can happen if another peer is behind a NAT or firewall, or if they are no longer online.
What's not expected is the way that the multiaddresses are being encoded as base64. I haven't seen this issue in a long time. What version of Mesh are you running?
@albrow : I think this happened because I'm calling over limit requests with infura provider for kovan testing. I've decreased the block pollling time to solve this issue.
Context
Running Mesh on the
development
branch by building from source, specifically at commit 94bb6ce0d3dbf273d84167cfec3bd80493fb8e60.Expected Behavior
All addresses being logged should be real addresses, even if the peer cannot be dialed at them.
Current Behavior
The logs show some addresses with what looks like base64 encoding. These are not dialable and won't work with the
go-multiaddr
package. Maybe the entries in the DHT are getting borked somehow? Or maybe the addresses themselves are fine and it's just a problem with how the logs are encoded?Failure Information (for bugs)
Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.
Steps to Reproduce
Please provide detailed steps for reproducing the issue.
make mesh && ETHEREUM_CHAIN_ID="1" ETHEREUM_RPC_URL="your RPC url here" VERBOSITY=5 mesh
."could not connect to peer"
messages.Failure Logs
Please include any relevant log snippets or files here.