Execute

Author: Mirko-von-Leipzig

bin/network-monitor/src/commands/start.rs

@@ -13,8 +13,8 @@ use crate::monitor::tasks::Tasks;
 
 /// Start the network monitoring service.
 ///
-/// This function initializes all monitoring tasks including RPC status checking,
-/// remote prover testing, faucet testing, and the web frontend.
+/// This function initializes all monitoring tasks including RPC status checking, remote prover
+/// testing, faucet testing, and the web frontend.
 #[instrument(target = COMPONENT, name = "start-monitor", skip_all, fields(port = %config.port))]
 pub async fn start_monitor(config: MonitorConfig) -> Result<()> {
     // Load configuration from command-line arguments and environment variables

bin/network-monitor/src/counter.rs

@@ -1,7 +1,7 @@
 //! Counter increment task functionality.
 //!
-//! This module contains the implementation for periodically incrementing the counter
-//! of the network account deployed at startup by creating and submitting network notes.
+//! This module contains the implementation for periodically incrementing the counter of the network
+//! account deployed at startup by creating and submitting network notes.
 
 use std::path::Path;
 use std::sync::Arc;
@@ -315,8 +315,8 @@ fn send_status(tx: &watch::Sender<ServiceStatus>, status: ServiceStatus) -> Resu
 
 /// Run the counter tracking task.
 ///
-/// This function periodically fetches the current counter value from the network
-/// and updates the tracking details.
+/// This function periodically fetches the current counter value from the network and updates the
+/// tracking details.
 ///
 /// # Arguments
 ///

bin/network-monitor/src/deploy/mod.rs

@@ -40,9 +40,8 @@ use crate::deploy::wallet::{create_wallet_account, save_wallet_account};
 pub mod counter;
 pub mod wallet;
 
-/// Create an RPC client configured with the correct genesis metadata in the
-/// `Accept` header so that write RPCs such as `SubmitProvenTransaction` are
-/// accepted by the node.
+/// Create an RPC client configured with the correct genesis metadata in the `Accept` header so that
+/// write RPCs such as `SubmitProvenTransaction` are accepted by the node.
 pub async fn create_genesis_aware_rpc_client(
     rpc_url: &Url,
     timeout: Duration,
@@ -98,9 +97,8 @@ pub async fn create_genesis_aware_rpc_client(
 
 /// Ensure accounts exist, creating them if they don't.
 ///
-/// This function checks if the wallet and counter account files exist.
-/// If they don't exist, it creates new accounts and saves them to the specified files.
-/// If they do exist, it does nothing.
+/// This function checks if the wallet and counter account files exist. If they don't exist, it
+/// creates new accounts and saves them to the specified files. If they do exist, it does nothing.
 ///
 /// # Arguments
 ///
@@ -141,8 +139,7 @@ pub async fn ensure_accounts_exist(
 
 /// Deploy counter account to the network.
 ///
-/// This function creates a counter program account,
-/// then saves it to the specified file.
+/// This function creates a counter program account, then saves it to the specified file.
 #[instrument(target = COMPONENT, name = "deploy-counter-account", skip_all, ret(level = "debug"))]
 pub async fn deploy_counter_account(counter_account: &Account, rpc_url: &Url) -> Result<()> {
     // Deploy counter account to the network using a genesis-aware RPC client.

bin/network-monitor/src/faucet.rs

@@ -1,7 +1,7 @@
 //! Faucet testing functionality.
 //!
-//! This module contains the logic for periodically testing faucet functionality
-//! by requesting proof-of-work challenges, solving them, and submitting token requests.
+//! This module contains the logic for periodically testing faucet functionality by requesting
+//! proof-of-work challenges, solving them, and submitting token requests.
 
 use std::time::Duration;
 

bin/network-monitor/src/main.rs

@@ -1,7 +1,7 @@
 //! Miden Network Monitor
 //!
-//! A monitor application for Miden network infrastructure that provides real-time status
-//! monitoring and account deployment capabilities.
+//! A monitor application for Miden network infrastructure that provides real-time status monitoring
+//! and account deployment capabilities.
 
 use anyhow::Result;
 use clap::Parser;
@@ -28,8 +28,8 @@ pub const COMPONENT: &str = "miden-network-monitor";
 
 /// Network Monitor main function.
 ///
-/// This function parses command-line arguments and delegates to the appropriate
-/// command handler. The monitor supports two main commands:
+/// This function parses command-line arguments and delegates to the appropriate command handler.
+/// The monitor supports two main commands:
 /// - `start`: Runs the network monitoring service with web dashboard
 /// - `deploy-account`: Creates and deploys Miden accounts to the network
 #[tokio::main]

bin/network-monitor/src/monitor/tasks.rs

@@ -355,8 +355,8 @@ impl Tasks {
 
 /// Gets the current Unix timestamp in seconds.
 ///
-/// This function is infallible - if the system time is somehow before Unix epoch
-/// (extremely unlikely), it returns 0.
+/// This function is infallible - if the system time is somehow before Unix epoch (extremely
+/// unlikely), it returns 0.
 pub fn current_unix_timestamp_secs() -> u64 {
     SystemTime::now()
         .duration_since(UNIX_EPOCH)

bin/network-monitor/src/remote_prover.rs

@@ -73,8 +73,8 @@ pub struct ProverTestDetails {
 
 /// Runs a task that continuously tests remote prover functionality and updates a watch channel.
 ///
-/// This function spawns a task that periodically sends mock request payloads to a remote prover
-/// and measures the success/failure rate and performance metrics for proof generation.
+/// This function spawns a task that periodically sends mock request payloads to a remote prover and
+/// measures the success/failure rate and performance metrics for proof generation.
 ///
 /// # Arguments
 ///
@@ -213,8 +213,8 @@ async fn test_remote_prover(
 
 /// Converts a `tonic::Status` error to a JSON string with structured error information.
 ///
-/// This function extracts the code, message, details, and metadata from a `tonic::Status`
-/// error and serializes them into a JSON string for structured error reporting.
+/// This function extracts the code, message, details, and metadata from a `tonic::Status` error and
+/// serializes them into a JSON string for structured error reporting.
 ///
 /// # Arguments
 ///
@@ -254,9 +254,9 @@ fn tonic_status_to_json(status: &tonic::Status) -> String {
 
 /// Generates a mock transaction for testing remote prover functionality.
 ///
-/// This function creates a mock transaction using `MockChainBuilder` similar to what's done
-/// in the remote prover tests. The transaction is generated once and can be reused for
-/// multiple proof test calls.
+/// This function creates a mock transaction using `MockChainBuilder` similar to what's done in the
+/// remote prover tests. The transaction is generated once and can be reused for multiple proof test
+/// calls.
 pub async fn generate_mock_transaction() -> anyhow::Result<TransactionInputs> {
     let mut mock_chain_builder = MockChainBuilder::new();
 

bin/network-monitor/src/status.rs

@@ -1,7 +1,7 @@
 //! Network monitor status checker.
 //!
-//! This module contains the logic for checking the status of network services.
-//! Individual status checker tasks send updates via watch channels to the web server.
+//! This module contains the logic for checking the status of network services. Individual status
+//! checker tasks send updates via watch channels to the web server.
 
 use std::time::Duration;
 
@@ -132,8 +132,8 @@ pub struct StoreStatusDetails {
 
 /// Details of a block producer service.
 ///
-/// This struct contains the details of a block producer service, which is a union of the details
-/// of the block producer service.
+/// This struct contains the details of a block producer service, which is a union of the details of
+/// the block producer service.
 #[derive(Debug, Clone, Serialize, Deserialize)]
 pub struct BlockProducerStatusDetails {
     pub version: String,
@@ -155,8 +155,8 @@ pub struct MempoolStatusDetails {
 
 /// Details of a remote prover service.
 ///
-/// This struct contains the details of a remote prover service, which is a union of the details
-/// of the remote prover service.
+/// This struct contains the details of a remote prover service, which is a union of the details of
+/// the remote prover service.
 #[derive(Debug, Clone, Serialize, Deserialize)]
 pub struct RemoteProverStatusDetails {
     pub url: String,
@@ -267,8 +267,8 @@ impl From<RpcStatus> for RpcStatusDetails {
 
 /// Runs a task that continuously checks RPC status and updates a watch channel.
 ///
-/// This function spawns a task that periodically checks the RPC service status
-/// and sends updates through a watch channel.
+/// This function spawns a task that periodically checks the RPC service status and sends updates
+/// through a watch channel.
 ///
 /// # Arguments
 ///
@@ -357,8 +357,8 @@ pub(crate) async fn check_rpc_status(
 
 /// Runs a task that continuously checks remote prover status and updates a watch channel.
 ///
-/// This function spawns a task that periodically checks a remote prover service status
-/// and sends updates through a watch channel.
+/// This function spawns a task that periodically checks a remote prover service status and sends
+/// updates through a watch channel.
 ///
 /// # Arguments
 ///

bin/remote-prover/src/api/prover.rs

@@ -50,8 +50,8 @@ impl std::str::FromStr for ProofType {
 
 /// The prover for the remote prover.
 ///
-/// This enum is used to store the prover for the remote prover.
-/// Only one prover is enabled at a time.
+/// This enum is used to store the prover for the remote prover. Only one prover is enabled at a
+/// time.
 enum Prover {
     Transaction(Mutex<LocalTransactionProver>),
     Batch(Mutex<LocalBatchProver>),

bin/remote-prover/src/proxy/mod.rs

@@ -243,9 +243,9 @@ static RATE_LIMITER: LazyLock<Rate> = LazyLock::new(|| Rate::new(Duration::from_
 // REQUEST QUEUE
 // ================================================================================================
 
-/// Request queue holds the list of requests that are waiting to be processed by the workers and
-/// the time they were enqueued.
-/// It is used to keep track of the order of the requests to then assign them to the workers.
+/// Request queue holds the list of requests that are waiting to be processed by the workers and the
+/// time they were enqueued. It is used to keep track of the order of the requests to then assign
+/// them to the workers.
 pub struct RequestQueue {
     queue: RwLock<VecDeque<(Uuid, Instant)>>,
 }
@@ -299,8 +299,8 @@ static QUEUE: LazyLock<RequestQueue> = LazyLock::new(RequestQueue::new);
 
 /// Pingora `RequestHeader` injector for OpenTelemetry trace context propagation.
 ///
-/// This allows the proxy to inject trace context into headers that will be forwarded
-/// to worker nodes, enabling proper parent-child trace relationships.
+/// This allows the proxy to inject trace context into headers that will be forwarded to worker
+/// nodes, enabling proper parent-child trace relationships.
 struct PingoraHeaderInjector<'a>(&'a mut pingora::http::RequestHeader);
 
 impl opentelemetry::propagation::Injector for PingoraHeaderInjector<'_> {
@@ -321,8 +321,8 @@ impl opentelemetry::propagation::Injector for PingoraHeaderInjector<'_> {
 /// Custom context for the request/response lifecycle
 ///
 /// We use this context to keep track of the number of tries for a request, the unique ID for the
-/// request, the worker that will process the request, a span that will be used for traces along
-/// the transaction execution, and a timer to track how long the request took.
+/// request, the worker that will process the request, a span that will be used for traces along the
+/// transaction execution, and a timer to track how long the request took.
 #[derive(Debug)]
 pub struct RequestContext {
     /// Number of tries for the request
@@ -362,9 +362,9 @@ impl RequestContext {
 
 /// Wrapper around the load balancer that implements the [`ProxyHttp`] trait
 ///
-/// This wrapper is used to implement the [`ProxyHttp`] trait for [`Arc<LoadBalancer>`].
-/// This is necessary because we want to share the load balancer between the proxy server and the
-/// health check background service.
+/// This wrapper is used to implement the [`ProxyHttp`] trait for [`Arc<LoadBalancer>`]. This is
+/// necessary because we want to share the load balancer between the proxy server and the health
+/// check background service.
 #[derive(Debug)]
 pub struct LoadBalancer(pub Arc<LoadBalancerState>);