Merged
Conversation
kderme
force-pushed
the
kderme/fix-epoch-stake
branch
2 times, most recently
from
674149d to
926ab41
Compare
Cmdv
approved these changes
Dec 12, 2025
kderme
force-pushed
the
kderme/fix-epoch-stake
branch
2 times, most recently
from
6786112 to
8f42113
Compare
kderme
force-pushed
the
kderme/fix-epoch-stake
branch
from
8f42113 to
23fbbbe
Compare
9 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #1678
Supersedes #1796
Depends on #2024
On each epoch boundary dbsync will compare the expected and actual number of epoch_stake. If it doesn't match it insert all entries again (after creating manual unique keys contraints)
This is on preprod: