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

Fix resyncing the ticket database after unexpected shutdown #157

Merged
merged 1 commit into from
May 6, 2016

Conversation

cjepson
Copy link
Contributor

@cjepson cjepson commented May 5, 2016

The ticket database would restore from the genesis block if it failed
the check to see if the tip matched with the database best block. This
corrects the resyncing such that if it finds a matching block for the
ticket database top block in the database, it instead resyncs from that
block instead of the genesis block.

@cjepson cjepson force-pushed the cj_050516fasttdbsync branch from 314f30c to f3f4005 Compare May 5, 2016 20:59
The ticket database would restore from the genesis block if it failed
the check to see if the tip matched with the database best block. This
corrects the resyncing such that if it finds a matching block for the
ticket database top block in the database, it instead resyncs from that
block instead of the genesis block.
@cjepson cjepson force-pushed the cj_050516fasttdbsync branch from f3f4005 to d7ef12f Compare May 5, 2016 21:05
@chappjc
Copy link
Member

chappjc commented May 5, 2016

tACK on testnet and mainnet
(d7ef12f)

@alexlyp
Copy link
Member

alexlyp commented May 6, 2016

tACK

@alexlyp alexlyp merged commit 1b8c661 into decred:master May 6, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants