lighthouse-pulse/beacon_node/lighthouse_network/src
Pawan Dhananjay f3439116da Return ResourceUnavailable if we are unable to reconstruct execution payloads (#3365)
## Issue Addressed

Resolves #3351 

## Proposed Changes

Returns a `ResourceUnavailable` rpc error if we are unable to serve full payloads to blocks by root and range requests because the execution layer is not synced.


## Additional Info

This PR also changes the penalties such that a `ResourceUnavailable` error is only penalized if it is an outgoing request. If we are syncing and aren't getting full block responses, then we don't have use for the peer. However, this might not be true for the incoming request case. We let the peer decide in this case if we are still useful or if we should be banned.
cc @divagant-martian please let me know if i'm missing something here.
2022-07-27 03:20:00 +00:00
..
behaviour Fix some typos (#3376) 2022-07-27 00:51:06 +00:00
discovery [refactor] Refactor Option/Result combinators (#3180) 2022-05-16 01:59:47 +00:00
peer_manager Return ResourceUnavailable if we are unable to reconstruct execution payloads (#3365) 2022-07-27 03:20:00 +00:00
rpc Use async code when interacting with EL (#3244) 2022-07-03 05:36:50 +00:00
types Bump the MSRV to 1.62 and using #[derive(Default)] on enums (#3304) 2022-07-15 07:31:19 +00:00
config.rs Filter non global ips from discovery (#3023) 2022-03-02 03:14:27 +00:00
lib.rs libp2p upgrade + gossipsub interval fix (#3012) 2022-02-10 04:12:03 +00:00
metrics.rs Retry gossipsub messages when insufficient peers (#2964) 2022-02-03 01:12:30 +00:00
service.rs Custom RPC request management for sync (#3029) 2022-03-02 22:07:17 +00:00