-
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
Free up the term 'replicate' for exclusive use in ledger replication #2057
Conversation
@pgarg66, added you to review in the context of counter names. There's no tests protecting those strings. The test suite lets me change them with no regard for the implications. |
@garious , changing the string names would also require to update metrics dashboard. |
359671e
to
54a1e5e
Compare
@sakridge, @sagar-solana, still waiting on you guys. Are you okay with these name changes? |
Also, align Sockets field names with ContactInfo.
54a1e5e
to
8614796
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.
lgtm
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
* Fix signer parameters (staker, manager, depositor, fee-payer, and token-owner) * On deposit / withdraw / add / remove validator, show the validator stake account and where the stake is going to
Bumps solana_rbpf to v0.8.2 and removes switch_to_new_elf_parser.
Problem
Replication code is using name "storage" to avoid interfering with the term replicate that's been awkwardly used by the TVU to describe the stage that replays the ledger.
Summary of Changes
ReplicateStage
toReplayStage
cc: #1409