syncer: fix issues when switching to core.Consensus (#418)

- when confirmed blocks passed to core.Consensus
   aren't continuous in position in some chain, the
   pulling would skip those missing blocks.
   - fix: when some block is missing, avoid adding it
      and all blocks after it to core.Consensus.
- we need to avoid the receive channel of network
   module full.
   - fix: during switching to core.Consensus, we
      need to launch a dummy receiver to receive
      from receive channel of network module.
   - fix: between the period during core.Consensus
      created and before running, a dummy receiver is
      also required to receive from receive channel of
      network module.

1 files changed, 1 insertions, 1 deletions

diff --git a/core/lattice-data.go b/core/lattice-data.go
index 998fb1f..8367539 100644
--- a/core/lattice-data.go
+++ b/core/lattice-data.go
@@ -55,7 +55,7 @@ type ErrAckingBlockNotExists struct {
 }
 
 func (e ErrAckingBlockNotExists) Error() string {
-	return fmt.Sprintf("acking block %s not exists", e.hash)
+	return fmt.Sprintf("acking block %s not exists", e.hash.String()[:6])
 }
 
 // Errors for method usage