don't logs ValsetUpToDate error

onomyprotocol · Apr 20, 2022 · bb5115d · bb5115d
1 parent 4c9e938
commit bb5115d
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 2 deletions.
diff --git a/orchestrator/cosmos_gravity/src/send.rs b/orchestrator/cosmos_gravity/src/send.rs
@@ -293,9 +293,9 @@ pub async fn send_ethereum_claims(
 
     let msgs: Vec<Msg> = ordered_msgs.into_iter().map(|(_, v)| v).collect();
 
-    Ok(contact
+    contact
         .send_message(&msgs, None, &[fee], Some(TIMEOUT), private_key)
-        .await?)
+        .await
 }
 
 /// Sends tokens from Cosmos to Ethereum. These tokens will not be sent immediately instead

diff --git a/orchestrator/relayer/src/valset_relaying.rs b/orchestrator/relayer/src/valset_relaying.rs
@@ -60,6 +60,9 @@ pub async fn relay_valsets(
     .await
     {
         Ok(v) => v,
+        // If we get the RecoverableError we don't need to log it, since it is a kind of flag to indicate that it was expected.
+        // And here we expect the ValsetUpToDate error which means that we don't need to update up to date valset.
+        Err(GravityError::RecoverableError(_)) => return,
         Err(e) => {
             error!(
                 "We were unable to find a valid validator set update to submit! {:?}",