Updating timeouts related to sync operations

Author: www

node/MwcNode.cpp

@@ -600,7 +600,7 @@ void MwcNode::nodeOutputGenericEvent( tries::NODE_OUTPUT_EVENT event, QString me
         case tries::NODE_OUTPUT_EVENT::RECEIVE_BLOCK_LISTEN:
         case tries::NODE_OUTPUT_EVENT::RECEIVE_BLOCK_START: {
             // expected no break
-            nextTimeLimit += int64_t(MWC_NODE_SYNC_MESSAGES * config::getTimeoutMultiplier());
+            nextTimeLimit += int64_t(RECEIVE_BLOCK_LISTEN * config::getTimeoutMultiplier());
             nodeOutOfSyncCounter = 0;
             break;
         }

node/MwcNode.h

@@ -43,8 +43,7 @@ const int64_t START_TOR_TIMEOUT = 60*10*1000; // Tor can start for a very long t
 
 // messages from NodeOutputParser
 const int64_t MWC_NODE_STARTED_TIMEOUT = 180*1000; // It can take some time to find peers
-const int64_t MWC_NODE_SYNC_MESSAGES = 60*1000; // Sync supposed to be agile
-const int64_t PIBD_IS_DONE = 30*60*1000; // That might take a while (10 minutes for Debug mwc app on MacBook Pro)
+const int64_t MWC_NODE_SYNC_MESSAGES = 5*60*1000; // Sync supposed to be agile
 const int64_t RECEIVE_BLOCK_LISTEN = 10*60*1000; // 10 minutes can be delay due non consistancy. API call expected to catch non sync cases
 const int64_t NETWORK_ISSUES = 0; // Let's not consider network issues. API call will restart the node