Call new_blocks even though block verification queue is not empty

new_blocks was called when the block verification queue is empty. The
purpose of the behavior is not clear. Maybe it was used to
backpressure for block sync extension. Since we have another block
sync flow control and tendermint assumes that new_blocks is always
called, this commit changed the behavior of new_blocks to be always called.

Author: majecty

core/src/client/importer.rs

@@ -144,7 +144,10 @@ impl Importer {
         };
 
         {
-            if !imported_blocks.is_empty() && is_empty {
+            if !imported_blocks.is_empty() {
+                if !is_empty {
+                    ctrace!(CLIENT, "Call new_blocks even though block verification queue is not empty");
+                }
                 let (enacted, retracted) = self.calculate_enacted_retracted(&import_results);
                 self.miner.chain_new_blocks(client, &imported_blocks, &invalid_blocks, &enacted, &retracted);
                 client.new_blocks(&imported_blocks, &invalid_blocks, &enacted, &retracted, &[], duration);