-
Notifications
You must be signed in to change notification settings - Fork 45
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
feat: On Demand Peer Discovery based on shard and service #834
Conversation
…ge inter-dependencies
Jenkins BuildsClick to see older builds (128)
|
return peerID, nil | ||
} else if !errors.Is(err, ErrNoPeersAvailable) { | ||
pm.logger.Debug("could not retrieve random peer from slot", zap.String("protocol", string(criteria.Proto)), | ||
zap.String("pubsubTopic", criteria.PubsubTopic), zap.Error(err)) |
Check failure
Code scanning / CodeQL
Log entries created from user input High
user-provided value
if err == nil { | ||
return peerID, nil | ||
} else { | ||
pm.logger.Debug("Discovering peers by pubsubTopic", zap.String("pubsubTopic", pubsubTopic)) |
Check failure
Code scanning / CodeQL
Log entries created from user input High
user-provided value
Co-authored-by: richΛrd <info@richardramos.me>
pm.logger.Error("failed to discover and conenct to peers", zap.Error(err)) | ||
} | ||
} else { | ||
pm.logger.Debug("failed to convert pubsub topic to shard as topic is named pubsubTopic", zap.String("topic", pubsubTopic)) |
Check failure
Code scanning / CodeQL
Log entries created from user input High
Description
Ability to discover peers on demand based on shard and service. This would help lightclients and relay nodes during new shard subscription in reducing wait time in discovery.
Changes
Tests