What the developer wrote
Authored by Jeffrey Czyz
Run rustfmt on fuzz
What changed, and why it matters
This commit only reformats code in test/fuzz files using rustfmt. It reorders import statements and wraps a constructor call across more lines. No program behavior, logic, or security properties are changed.
No security action needed. This is a code-style/formatting commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff shows pure formatting changes produced by rustfmt in three fuzz targets: chanmon_consistency.rs, full_stack.rs, and lsps_message.rs. Imports are alphabetically reordered (TransactionType moved last) and one Arc::new(LiquidityManagerSync::new(…).unwrap()) call is rewrapped with additional indentation. No functional code, types, call order, or error handling changed.
Changed components
fuzz/src/chanmon_consistency.rsfuzz/src/full_stack.rsfuzz/src/lsps_message.rsInspect captured patch +16 / −13
diff --git a/fuzz/src/chanmon_consistency.rs b/fuzz/src/chanmon_consistency.rs
index 87d58da..bb80004 100644
--- a/fuzz/src/chanmon_consistency.rs
+++ b/fuzz/src/chanmon_consistency.rs
@@ -37,7 +37,7 @@ use lightning::blinded_path::message::{BlindedMessagePath, MessageContext, Messa
use lightning::blinded_path::payment::{BlindedPaymentPath, ReceiveTlvs};
use lightning::chain;
use lightning::chain::chaininterface::{
- TransactionType, BroadcasterInterface, ConfirmationTarget, FeeEstimator,
+ BroadcasterInterface, ConfirmationTarget, FeeEstimator, TransactionType,
};
use lightning::chain::channelmonitor::{ChannelMonitor, MonitorEvent};
use lightning::chain::transaction::OutPoint;
diff --git a/fuzz/src/full_stack.rs b/fuzz/src/full_stack.rs
index 11eca60..c55da4f 100644
--- a/fuzz/src/full_stack.rs
+++ b/fuzz/src/full_stack.rs
@@ -36,7 +36,7 @@ use lightning::blinded_path::message::{BlindedMessagePath, MessageContext, Messa
use lightning::blinded_path::payment::{BlindedPaymentPath, ReceiveTlvs};
use lightning::chain;
use lightning::chain::chaininterface::{
- TransactionType, BroadcasterInterface, ConfirmationTarget, FeeEstimator,
+ BroadcasterInterface, ConfirmationTarget, FeeEstimator, TransactionType,
};
use lightning::chain::chainmonitor;
use lightning::chain::transaction::OutPoint;
diff --git a/fuzz/src/lsps_message.rs b/fuzz/src/lsps_message.rs
index 547a27b..8371d1c 100644
--- a/fuzz/src/lsps_message.rs
+++ b/fuzz/src/lsps_message.rs
@@ -77,17 +77,20 @@ pub fn do_test(data: &[u8]) {
genesis_block.header.time,
));
- let liquidity_manager = Arc::new(LiquidityManagerSync::new(
- Arc::clone(&keys_manager),
- Arc::clone(&keys_manager),
- Arc::clone(&manager),
- None::<Arc<dyn Filter + Send + Sync>>,
- None,
- kv_store,
- Arc::clone(&tx_broadcaster),
- None,
- None,
- ).unwrap());
+ let liquidity_manager = Arc::new(
+ LiquidityManagerSync::new(
+ Arc::clone(&keys_manager),
+ Arc::clone(&keys_manager),
+ Arc::clone(&manager),
+ None::<Arc<dyn Filter + Send + Sync>>,
+ None,
+ kv_store,
+ Arc::clone(&tx_broadcaster),
+ None,
+ None,
+ )
+ .unwrap(),
+ );
let mut reader = data;
if let Ok(Some(msg)) = liquidity_manager.read(LSPS_MESSAGE_TYPE_ID, &mut reader) {
let secp = Secp256k1::signing_only();
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.