-
Notifications
You must be signed in to change notification settings - Fork 39
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(drive): apply batch is not using transaction in remove_all_votes_given_by_identities
#2309
Conversation
…es_given_by_identities
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
remove_all_votes_given_by_identities
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.
👍
…_given_by_identities` (#2309) Co-authored-by: Ivan Shumkov <ivan@shumkov.ru>
Issue being fixed or feature implemented
We had a sequence of errors on the mainnet started since block 32326. We got RocksDB's "transaction is busy" error because we removed votes without using a database transaction. Due to another bug in Tenderdash (dashpay/tenderdash#966), validators just proceeded to the next block partially committing the state and updating the cache. Full nodes are stuck and proceeded after re-sync.
What was done?
How Has This Been Tested?
Syncing testnet and mainnet
Breaking Changes
None
Checklist:
For repository code-owners and collaborators only