eth: when snap is complaining for missing eth, be verbose about the details #28249
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We have a warning log if somebody connects on snap but doe snot have a valid eth to go along, since the two protocols need each other. This PR extends that log so we can see what exactly is the mismatch to see who the offenders are. It does not make the log less annoying, but that will be solved in a followup PR that does some ENR checks. Then we can see how frequent it remains and what to do about it.
Turns out doing the ENR check also requires exposing devp2p caps into the ENR records. That is going to have to be done on all clients, so it's going to take a while, so for now this PR lowers the warning down to debug. We can revisit when ENR caps are more prevalent.