cargo fix and some test fixes

beacon_node/network/src/beacon_processor/mod.rs

@@ -60,7 +60,7 @@ use std::task::Context;
 use std::time::Duration;
 use std::{cmp, collections::HashSet};
 use task_executor::TaskExecutor;
-use tokio::sync::{mpsc, oneshot};
+use tokio::sync::{mpsc};
 use types::{
     Attestation, AttesterSlashing, BlobsSidecar, Hash256, ProposerSlashing,
     SignedAggregateAndProof, SignedBeaconBlock, SignedContributionAndProof, SignedVoluntaryExit,

beacon_node/network/src/beacon_processor/worker/gossip_methods.rs

@@ -695,13 +695,13 @@ impl<T: BeaconChainTypes> Worker<T> {
     #[allow(clippy::too_many_arguments)]
     pub fn process_gossip_blob(
         self,
-        message_id: MessageId,
-        peer_id: PeerId,
-        peer_client: Client,
-        blob: BlobsSidecar<T::EthSpec>,
-        reprocess_tx: mpsc::Sender<ReprocessQueueMessage<T>>,
-        duplicate_cache: DuplicateCache,
-        seen_duration: Duration,
+        _message_id: MessageId,
+        _peer_id: PeerId,
+        _peer_client: Client,
+        _blob: BlobsSidecar<T::EthSpec>,
+        _reprocess_tx: mpsc::Sender<ReprocessQueueMessage<T>>,
+        _duplicate_cache: DuplicateCache,
+        _seen_duration: Duration,
     ) {
         //FIXME(sean)
     }

beacon_node/network/src/beacon_processor/worker/rpc_methods.rs

@@ -125,9 +125,9 @@ impl<T: BeaconChainTypes> Worker<T> {
 
     pub fn handle_tx_blobs_by_range_request(
         &self,
-        peer_id: PeerId,
-        request_id: PeerRequestId,
-        mut req: TxBlobsByRangeRequest,
+        _peer_id: PeerId,
+        _request_id: PeerRequestId,
+        _req: TxBlobsByRangeRequest,
     ) {
         //FIXME(sean)
     }

beacon_node/network/src/sync/manager.rs

@@ -53,7 +53,7 @@ use std::ops::Sub;
 use std::sync::Arc;
 use std::time::Duration;
 use tokio::sync::mpsc;
-use types::{BlobsSidecar, Epoch, EthSpec, Hash256, SignedBeaconBlock, Slot};
+use types::{BlobsSidecar, EthSpec, Hash256, SignedBeaconBlock, Slot};
 
 /// The number of slots ahead of us that is allowed before requesting a long-range (batch)  Sync
 /// from a peer. If a peer is within this tolerance (forwards or backwards), it is treated as a