Continuous false positives will lead to them being ignored entirely. Better to disable now until this can be fixed more thoroughly in the next release.
Discussed at 2016-03-31 IRC meeting.
Refs: #7568
utACK
Continuous false positives lead to them being ignored entirely
so it's better to disable now until this can be fixed more
thoroughly.
1644 | @@ -1645,10 +1645,10 @@ bool AppInit2(boost::thread_group& threadGroup, CScheduler& scheduler) 1645 | StartNode(threadGroup, scheduler); 1646 | 1647 | // Monitor the chain, and alert if we get blocks much quicker or slower than expected 1648 | - int64_t nPowTargetSpacing = Params().GetConsensus().nPowTargetSpacing; 1649 | - CScheduler::Function f = boost::bind(&PartitionCheck, &IsInitialBlockDownload, 1650 | - boost::ref(cs_main), boost::cref(pindexBestHeader), nPowTargetSpacing); 1651 | - scheduler.scheduleEvery(f, nPowTargetSpacing); 1652 | + //int64_t nPowTargetSpacing = Params().GetConsensus().nPowTargetSpacing;
maybe add a comment why we outcomment that part for 0.12.x
OK
Done.
utACK new comment
utACK but #7568 should be milestoned to 0.13 before this is merged.