-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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 - Bank::compute_active_feature_set()
and Bank::apply_feature_activations()
#34124
Conversation
…ure_set() into Bank::apply_feature_activations().
I'm inclined to think this unit test will now fail: solana/runtime/src/bank/tests.rs Line 7727 in e589c07
Aside from |
You're right. That test is failing. |
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## master #34124 +/- ##
=========================================
- Coverage 81.9% 81.9% -0.1%
=========================================
Files 816 816
Lines 219753 219759 +6
=========================================
+ Hits 180001 180004 +3
- Misses 39752 39755 +3 |
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.
Looks good to me!
…ctivations()` (#34124) * Moves modification of feature accounts from Bank::compute_active_feature_set() into Bank::apply_feature_activations(). * Renames allow_new_activations and newly_activated to include_pending and pending. * Fix test_compute_active_feature_set. (cherry picked from commit 6b85450)
…ature_activations()` (backport of #34124) (#34136) Fix - `Bank::compute_active_feature_set()` and `Bank::apply_feature_activations()` (#34124) * Moves modification of feature accounts from Bank::compute_active_feature_set() into Bank::apply_feature_activations(). * Renames allow_new_activations and newly_activated to include_pending and pending. * Fix test_compute_active_feature_set. (cherry picked from commit 6b85450) Co-authored-by: Alexander Meißner <AlexanderMeissner@gmx.net>
Problem
A feature activation on devnet diverged because it was activated before the epoch boundary on part of the cluster (version dependent). This happened because of the backport #34003 which depends on
Bank::compute_active_feature_set()
being without side effects (as the name suggests).Summary of Changes
Move the actual activation of pending features from
Bank::compute_active_feature_set()
intoBank::apply_feature_activations()
.