From f7cd6874d976d552519328a88cc0635e8f3dbc16 Mon Sep 17 00:00:00 2001 From: plebhash Date: Wed, 24 Jul 2024 13:15:46 -0400 Subject: [PATCH] use handle_result! macro following suggestion by @lorbax https://github.com/stratum-mining/stratum/pull/1025#issuecomment-2245767959 the implementation diverged a bit from the suggestion, but it was still a good reminder that we should leverage `handle_result!` macro here --- roles/jd-server/src/lib/job_declarator/mod.rs | 11 ++++------- 1 file changed, 4 insertions(+), 7 deletions(-) diff --git a/roles/jd-server/src/lib/job_declarator/mod.rs b/roles/jd-server/src/lib/job_declarator/mod.rs index 4e4dad99c2..dbfce89a67 100644 --- a/roles/jd-server/src/lib/job_declarator/mod.rs +++ b/roles/jd-server/src/lib/job_declarator/mod.rs @@ -289,10 +289,7 @@ impl JobDeclaratorDownstream { new_block_sender.send(hexdata).await; } Err(e) => { - error!( - "Received solution but encountered error: {:?}", - e - ); + handle_result!(tx_status, Err(*e)) } }; } @@ -322,9 +319,9 @@ impl JobDeclaratorDownstream { let _ = new_block_sender.send(hexdata).await; }, Err(e) => { - error!( - "Error retrieving transactions: {:?}", - e + handle_result!( + tx_status, + Err(*e) ); } };