-
Notifications
You must be signed in to change notification settings - Fork 112
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
Added "is RPL Locking Allowed" check to every PDAOCanProposeXYZ
function
#506
Conversation
add is RPL Locking Allowed check to proposeSetting
add is RPL Locking Allowed check to proposeSecurityCouncilInvite
add RPL Locking Allowed check to proposeRecurringSpend
add RPL Locking Allowed check to proposeSecurityCouncilReplace
var wg errgroup.Group | ||
|
||
// Get is RPL locking allowed | ||
wg.Go(func() error { |
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.
You usually want to use goroutines when starting multiple queries at the same time. If you have only one query then you don't need to use threads.
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.
Thanks for the tip! I've fixed the usage of goroutines.
PDAO functions edited:
Haven't tested these 3 yet:- Propose Sec Council Kick- Propose Recurring Spend Update- Propose Sec Council Updatefixed usage of goroutines per Fornax's suggestion!