lighthouse/beacon_node/http_api
Paul Hauner c973bfc90c Reduce log severity for late and unrevealed blocks (#3775)
## Issue Addressed

NA

## Proposed Changes

In #3725 I introduced a `CRIT` log for unrevealed payloads, against @michaelsproul's [advice](https://github.com/sigp/lighthouse/pull/3725#discussion_r1034142113). After being woken up in the middle of the night by a block that was not revealed to the BN but *was* revealed to the network, I have capitulated. This PR implements @michaelsproul's suggestion and reduces the severity to `ERRO`.

Additionally, I have dropped a `CRIT` to an `ERRO` for when a block is published late. The block in question was indeed published late on the network, however now that we have builders that can slow down block production I don't think the error is "actionable" enough to warrant a `CRIT` for the user.

## Additional Info

NA
2022-12-10 00:45:18 +00:00
..
src Reduce log severity for late and unrevealed blocks (#3775) 2022-12-10 00:45:18 +00:00
tests Health Endpoints for UI (#3668) 2022-11-15 05:21:26 +00:00
Cargo.toml Health Endpoints for UI (#3668) 2022-11-15 05:21:26 +00:00