[BUG] Relayer panics and stops when it hits RPC Rate-Limit

[shekohex]

Overview

Relayer fails to Deserialize the RPC Response and panics with this error:

Error: Deserialization Error: response must be either a success/error or notification object at line 1 column 108. Response: {"jsonrpc":"2.0","error":{"code":429,"message":"Public RPC Rate Limit Hit, limit will reset in 60 seconds"}}

Logs

  2023-05-03T13:03:52.867389Z  WARN webb_relayer: Failed to load .env file: path not found
    at services/webb-relayer/src/main.rs:42

  2023-05-03T13:03:52.867439Z DEBUG webb_relayer_config::cli: Getting default dirs for webb relayer
    at crates/relayer-config/src/cli.rs:61

  2023-05-03T13:03:52.960171Z  INFO webb_relayer::service: Starting the server on 0.0.0.0:9955
    at services/webb-relayer/src/service/mod.rs:75

  2023-05-03T13:03:52.968958Z DEBUG webb_relayer::service::evm: Starting Background Services for (srcoll) chain.
    at services/webb-relayer/src/service/evm.rs:81

  2023-05-03T13:03:53.072809Z DEBUG webb_relayer::service::evm: VAnchor events watcher for (0x38e7…463d) Started.
    at services/webb-relayer/src/service/evm.rs:167

  2023-05-03T13:03:53.073683Z DEBUG webb_relayer::service::evm: Signature Bridge watcher for (0x441f…d69d) Started.
    at services/webb-relayer/src/service/evm.rs:455

  2023-05-03T13:03:53.074586Z DEBUG webb_relayer::service::evm: Transaction Queue for (534353) Started.
    at services/webb-relayer/src/service/evm.rs:526

  2023-05-03T13:03:53.095670Z DEBUG webb_relayer::service::evm: Starting Background Services for (arbitrum) chain.
    at services/webb-relayer/src/service/evm.rs:81

Error: Deserialization Error: response must be either a success/error or notification object at line 1 column 108. Response: {"jsonrpc":"2.0","error":{"code":429,"message":"Public RPC Rate Limit Hit, limit will reset in 60 seconds"}}

Stack backtrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>

[shekohex]

A possible solution for this bug is to use a RetryClient