Skip to content
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

ImmutableDB: truncate blocks from the future #1563

Merged
merged 4 commits into from Feb 4, 2020
Merged

Conversation

mrBliss
Copy link
Contributor

@mrBliss mrBliss commented Feb 3, 2020

Fixes #1550.

During validation, truncate any blocks >= the current (wall clock) slot.

@mrBliss mrBliss added the consensus issues related to ouroboros-consensus label Feb 3, 2020
@mrBliss mrBliss requested a review from edsko February 3, 2020 17:12
This groups all things the real ImmutableDB implementation needs to run
commands.
Copy link
Contributor

@edsko edsko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed over hangout.

It was defined in `ChainDB.StateMachine`. We'll need it in
`ImmutableDB.StateMachine` too.
During validation, truncate any blocks > the current (wall clock) slot.
@mrBliss
Copy link
Contributor Author

mrBliss commented Feb 4, 2020

bors r+

iohk-bors bot added a commit that referenced this pull request Feb 4, 2020
1563:  ImmutableDB: truncate blocks from the future  r=mrBliss a=mrBliss

Fixes #1550.

During validation, truncate any blocks >= the current (wall clock) slot.

Co-authored-by: Thomas Winant <thomas@well-typed.com>
@iohk-bors
Copy link
Contributor

iohk-bors bot commented Feb 4, 2020

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
consensus issues related to ouroboros-consensus
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Immutable DB: Validate that the DB does not contain any blocks from the future
2 participants