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

keep track of the last applied checkpoint in the chain follower #1807

Merged
merged 1 commit into from
Jun 27, 2020

Conversation

KtorZ
Copy link
Member

@KtorZ KtorZ commented Jun 26, 2020

Issue Number

#1796

Overview

  • 6a1f20e
    📍 keep track of the last applied checkpoint in the chain follower
    So that we avoid discarding rollbacks when they occur beyond the initial step.

Comments

So that we avoid discarding rollbacks when they occur beyond the initial step.
@KtorZ KtorZ added the RESOLVING ISSUE Mark a PR as resolving issues, for auto-generated CHANGELOG label Jun 26, 2020
@KtorZ KtorZ requested a review from Anviking June 26, 2020 21:53
@KtorZ KtorZ self-assigned this Jun 26, 2020
@@ -361,27 +361,27 @@ follow nl tr cps yield header =
where
eT = T.pack (show e)

step :: Int -> Cursor target -> IO FollowExit
step delay cursor = runExceptT (nextBlocks nl cursor) >>= \case
step :: Int -> [BlockHeader] -> Cursor target -> IO FollowExit
Copy link
Member

Choose a reason for hiding this comment

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

I think [BlockHeader] is a very confusing type here. Can we not have BlockHeader and call it say followerTip?

Copy link
Member

Choose a reason for hiding this comment

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

Gets a bit weird with the last cps0 not necessarily being apart of the chain though

@iohk-bors iohk-bors bot merged commit 6a1f20e into master Jun 27, 2020
@iohk-bors iohk-bors bot deleted the KtorZ/1796/conflicting-pool-production branch June 27, 2020 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RESOLVING ISSUE Mark a PR as resolving issues, for auto-generated CHANGELOG
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants