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.
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
[Dynamic Protocol State]
EpochStateContainer
stores epoch active identities #4834[Dynamic Protocol State]
EpochStateContainer
stores epoch active identities #4834Changes from 18 commits
ff90836
d8046b5
641dbca
dd04ca4
e765750
09fdfbe
d9ae36d
15e3e33
0dd823a
d3aa8d4
95dbf1e
df2bfab
25624f2
f92636d
0172dd1
d51fcfa
f6d519b
49934ce
c638874
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
Large diffs are not rendered by default.
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 am a little worried about this:
At this point, we don't know that the
updater
's internal state is a valid Protocol State. For all we know, it could be complete garbage. There is no atomicity requirement on theStateUpdater
as far as I can tell, in that it either applies the update entirely or not at all.Suggestion:
InvalidStateTransitionAttempted
totrue
).Updater
to "drop all modifications ifInvalidStateTransitionAttempted
" and document this properly throughout the code base. In a nutshell, within theBuild
method I would check thestate.InvalidStateTransitionAttempted
first; in that case we could just return a copy of theparentState
with only thestate.InvalidStateTransitionAttempted
set to true.Updater
, the corresponding interface, and ideally also the places where we call theUpdater
Further thoughts:
InvalidStateTransitionAttempted
, should the updater maybe already set its ownInvalidStateTransitionAttempted
flag? We would still raise the error to signal the failure to the caller. However, the caller would no longer be required to explicitly callupdater.SetInvalidStateTransitionAttempted()
(I'd leave that method, to allowUpdater
external logic to set this flag for other reasons).I think we should not do this as part of the current PR. The PR is already big enough and we keep layering on changes which makes it hard to keep track of without re-reviewing the entire PR. Added todo to #4649