-
Notifications
You must be signed in to change notification settings - Fork 259
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
Remove overly restrictive check_account_access for partitioned epoch rewards #631
Remove overly restrictive check_account_access for partitioned epoch rewards #631
Conversation
b4ea440
to
2cf1d93
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #631 +/- ##
========================================
Coverage 81.9% 81.9%
========================================
Files 851 851
Lines 230475 230724 +249
========================================
+ Hits 188785 188995 +210
- Misses 41690 41729 +39 |
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.
lgtm, sorry didn't realize splitting up the change would make the test migration a pain
2cf1d93
to
1b404d5
Compare
Thanks! Force-pushed to get rid of the wip commit, so unfortunately need one of you to re- ✅ |
Problem
As per SIMD-0118, credits to stake accounts should be allowed during the rewards interval. The current implementation Errors all transactions that load a stake account as writable, overly restrictive.
Summary of Changes
Remove existing check_account_access() call in SVM
I did leave this method in the TransactionProcessingCallback trait, however. It's a generic-enough name that it could be used for something other than rewards-period restriction.
The test changes in this PR need rebasing on #617 to pick up the StakeError; I've included a temporary WIP commit to allow this to pass CI (and still demonstrate the change in logic here) in the meantime.DoneTowards #426