Hopefully prevent a jump forward at the end of the consensus process.

If not, at least figure out exactly where in the consensus state machine that's happening.
This commit is contained in:
JoelKatz
2013-02-24 13:47:21 -08:00
parent 7b1dd394ea
commit 92be1c70f5

View File

@@ -373,7 +373,7 @@ void LedgerConsensus::checkLCL()
uint256 netLgr = mPrevLedgerHash;
int netLgrCount = 0;
uint256 favoredLedger = (mState == lcsPRE_CLOSE) ? uint256() : mPrevLedgerHash; // Don't get stuck one ledger back
uint256 favoredLedger = mPrevLedgerHash; // Don't get stuck one ledger back or jump one forward
boost::unordered_map<uint256, currentValidationCount> vals =
theApp->getValidations().getCurrentValidations(favoredLedger);
@@ -397,7 +397,7 @@ void LedgerConsensus::checkLCL()
default: status = "unknown";
}
cLog(lsWARNING) << "View of consensus changed during consensus (" << netLgrCount << ") status="
cLog(lsWARNING) << "View of consensus changed during " << status << " (" << netLgrCount << ") status="
<< status << ", " << (mHaveCorrectLCL ? "CorrectLCL" : "IncorrectLCL");
cLog(lsWARNING) << mPrevLedgerHash << " to " << netLgr;