-
Notifications
You must be signed in to change notification settings - Fork 193
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
features: sync with agave #1700
Conversation
6788329
to
11d08dd
Compare
We cannot reorganize/cleanup this file without regenerating the native program tests... My suggestion is to try to limit the scope of the changes to the feature_map to changing the public keys and adding new things at the end |
b1161aa
to
3dfa483
Compare
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.
I think we need a way of distinguishing between "cleaned up" (removed after activation - hardcoded to default activated) and "removed" (anza has reverted the code for these features, and never activated them, so they are no longer even present in anza's feature gate list).
137e2b9
to
70c671c
Compare
c990127
to
2f3687c
Compare
@lheeger-jump please fix CI |
|
85c34cb
to
de0f38a
Compare
56f3ca2
to
15967f6
Compare
bf12016
to
b1bcd78
Compare
Updated feature gates to stay in sync with agave:
"reverted":1
the features that got deleted (never activated)Update
timely_vote_credits
pubkey. Context: anza-xyz/agave#127Left as independent issue: #1906