-
Notifications
You must be signed in to change notification settings - Fork 198
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
cmd, epochStart, integrationTests: fix failed activation #3182
Conversation
Codecov Report
@@ Coverage Diff @@
## master #3182 +/- ##
=======================================
Coverage 75.37% 75.37%
=======================================
Files 630 630
Lines 61791 61796 +5
=======================================
+ Hits 46573 46578 +5
Misses 11064 11064
Partials 4154 4154
Continue to review full report at Codecov.
|
epochStart/metachain/rewardsV2.go
Outdated
@@ -56,19 +54,15 @@ func NewRewardsCreatorV2(args RewardsCreatorArgsV2) (*rewardsCreatorV2, error) { | |||
if check.IfNil(args.EconomicsDataProvider) { | |||
return nil, epochStart.ErrNilEconomicsDataProvider | |||
} | |||
if args.TopUpGradientPoint.Cmp(zero) < 0 { | |||
if check.IfNil(args.RewardsHandler) { | |||
return nil, epochStart.ErrInvalidRewardsTopUpGradientPoint |
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.
Wrong error message
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.
done
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 we test by moving the activation period after staking v3.5? With one epoch at least?
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.
System test passed.
This PR activates the APR changes which failed to activate previously due to some duplicated code.
Duplicated code was removed and rewards computation uses the common handler which is aware of the changed parameters.