BLOCK_ERROR_DATA_UNAVAILABLE errors if blobs are late about lodestar HOT 3 CLOSED

To be clear, seeing that in the logs does not mean anything is wrong?

Yes, there is nothing wrong on your end, this happens if we receive a block from a peer but the blobs are not received within 3 seconds of the slot.

We will then throw this error to trigger unknown block/blobs sync to request the data from others peers

But even though we do that, we still log it as an error which I believe we have to handle differently

We could consider logging block validation errors due to bad blocks we receive from the network as a warning instead of error, and for this specific case we might even use a debug log as it seems to be quite common error on goerli / holesky.

from lodestar.

To be clear, seeing that in the logs does not mean anything is wrong?

If it continues to be printed, a message after BLOCK_ERROR_DATA_UNAVAILABLE confirming it won't affect operation would be appreciated.

from lodestar.

The error log doesn't fit our logging policy. Should probably be a debug level log

from lodestar.