-
Notifications
You must be signed in to change notification settings - Fork 550
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
Fix libp2p initial peers RPC is triggered now #6702
Conversation
@@ -1122,7 +1115,7 @@ func main() { | |||
logging.SetLogLevel("autorelay", "info") // Logs relayed byte counts spammily | |||
logging.SetLogLevel("providers", "debug") | |||
logging.SetLogLevel("dht/RtRefreshManager", "warn") // Ping logs are spammy at debug, cpl logs are spammy at info | |||
logging.SetLogLevel("dht", "info") // Logs every operation to debug | |||
logging.SetLogLevel("dht", "debug") // Logs every operation to debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Will we want to leave these logs enabled, or is this just for testing? It's nice to not have the logspam if we aren't going to be using them.
@@ -1122,7 +1115,6 @@ func main() { | |||
logging.SetLogLevel("autorelay", "info") // Logs relayed byte counts spammily | |||
logging.SetLogLevel("providers", "debug") | |||
logging.SetLogLevel("dht/RtRefreshManager", "warn") // Ping logs are spammy at debug, cpl logs are spammy at info | |||
logging.SetLogLevel("dht", "info") // Logs every operation to debug |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you re-add this? This sets the minimum level, so deleting it shows all logs from the subsystem.
Tries triggering RPC for real with foundPeer on connect and disconnect
EDIT: Tested on
peering
network (which partially deployed). Confirmed that (1) the network peers metric increases (this means the callback is called properly). (2) the get some initial peers call is happening (3) it is successfully sending peers back to those that join on first connect and (4) there are no errors when trying to add those peers.