-
Notifications
You must be signed in to change notification settings - Fork 684
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
Add a bootnodes config validation #1655
Comments
@chefsale Are you working on this already? Please let us know. Thanks! |
I haven't started working on this, I just added th boot nodee to the init command. Is this urgent, if yes I can takr it over. |
No it is not urgent. Just want to make sure that it is still relevant |
This issue has been automatically marked as stale because it has not had recent activity in the last 2 months. |
@bowenwang1996 @janewang I will like to work on this issue . May you guide me what changes I have to make in which file to solve this issue ? |
I think it is about making sure that the ip address can be properly parsed. Actually it seems that this has already been fixed. @Rishabhraghwendra18 maybe you can help verify that |
@bowenwang1996 yup sure... I think you are correct it has been implemented . I have found this PR which talks about |
@Rishabhraghwendra18 thanks! closing this issue as it is already implemented |
Add a bootnode config validation. account_id cannot be
Some("34.89.175.66 :24567")
and address must be defined.[2019-11-06T11:06:42Z WARN near_network::peer_manager] Trying to connect to peer with no public address: PeerInfo { id: ed25519:FF7ttcBjsyNtXh6fBw5q85o2HYgtPxnC36Xhvt3HYb8X, addr: None, account_id: Some("34.89.175.66 :24567") }
The text was updated successfully, but these errors were encountered: