63eeb14a81
## Issue Addressed N/A ## Proposed Changes There seemed to be confusion among discord users on the eth1 fallback logging ``` WARN Error connecting to eth1 node. Trying fallback ..., endpoint: http://127.0.0.1:8545/, service: eth1_rpc ``` The assumption users seem to be making here is that it is trying the fallback and fallback=endpoint in the log. This PR improves the logging to be like ``` WARN Error connecting to eth1 node endpoint, endpoint: http://127.0.0.1:8545/, action: trying fallbacks, service: eth1_rpc ``` I think this is a bit more clear that the endpoint that failed is the one in the log. |
||
---|---|---|
.. | ||
beacon_chain | ||
client | ||
eth1 | ||
eth2_libp2p | ||
genesis | ||
http_api | ||
http_metrics | ||
network | ||
operation_pool | ||
src | ||
store | ||
tests | ||
timer | ||
websocket_server | ||
Cargo.toml |