Update fast-sync after latest polkadot-sdk

crates/subspace-service/src/lib.rs

@@ -75,7 +75,7 @@ use sc_proof_of_time::source::gossip::pot_gossip_peers_set_config;
 use sc_proof_of_time::source::{PotSlotInfo, PotSourceWorker};
 use sc_proof_of_time::verifier::PotVerifier;
 use sc_service::error::Error as ServiceError;
-use sc_service::{ClientExt, Configuration, NetworkStarter, SpawnTasksParams, TaskManager};
+use sc_service::{Configuration, NetworkStarter, SpawnTasksParams, TaskManager};
 use sc_subspace_block_relay::{
     build_consensus_relay, BlockRelayConfigurationError, NetworkWrapper,
 };
@@ -722,15 +722,6 @@ where
         mut telemetry,
     } = other;
 
-    // TODO: This will not be needed once we clear block gap correctly after sync is done
-    if config.sync == ChainSyncMode::Snap {
-        let info = client.info();
-        if info.best_hash != info.genesis_hash {
-            debug!(?info, "Clear block gap after fast-sync");
-            client.clear_block_gap();
-        }
-    }
-
     let offchain_indexing_enabled = config.offchain_worker.indexing_enabled;
     let (node, bootstrap_nodes) = match config.subspace_networking {
         SubspaceNetworking::Reuse {

crates/subspace-service/src/sync_from_dsn/fast_sync.rs

@@ -304,7 +304,7 @@ where
     // Clear the block gap that arises from first block import with a much higher number than
     // previously (resulting in a gap)
     // TODO: This is a hack and better solution is needed: https://github.com/paritytech/polkadot-sdk/issues/4407
-    client.clear_block_gap();
+    client.clear_block_gap()?;
 
     debug!(info = ?client.info(), "Fast sync finished successfully");