2de26b20f8
## Issue Addressed - Resolves #3266 ## Proposed Changes Return 200 OK rather than an error when a block, attestation or sync message is already known. Presently, we will log return an error which causes a BN to go "offline" from the VCs perspective which causes the fallback mechanism to do work to try and avoid and upcheck offline nodes. This can be observed as instability in the `vc_beacon_nodes_available_count` metric. The current behaviour also causes scary logs for the user. There's nothing to *actually* be concerned about when we see duplicate messages, this can happen on fallback systems (see code comments). ## Additional Info NA |
||
---|---|---|
.. | ||
attestation_performance.rs | ||
attester_duties.rs | ||
block_id.rs | ||
block_packing_efficiency.rs | ||
block_rewards.rs | ||
database.rs | ||
lib.rs | ||
metrics.rs | ||
proposer_duties.rs | ||
publish_blocks.rs | ||
state_id.rs | ||
sync_committees.rs | ||
validator_inclusion.rs | ||
version.rs |