ERRO Banning a disconnected peer #2046
Comments
|
Yeah, this can happen with events being built up and being processed spontaneously. This is harmless, but the situation wasn't considered when adding the error message in. |
bors bot
pushed a commit
that referenced
this issue
Dec 8, 2020
## Issue Addressed #2046 ## Proposed Changes The log was originally intended to verify the correct logic and ordering of events when scoring peers. The queued tasks can be structured in such a way that peers can be banned after they are disconnected. Therefore the error log is now downgraded to debug log.
bors bot
pushed a commit
that referenced
this issue
Dec 8, 2020
## Issue Addressed #2046 ## Proposed Changes The log was originally intended to verify the correct logic and ordering of events when scoring peers. The queued tasks can be structured in such a way that peers can be banned after they are disconnected. Therefore the error log is now downgraded to debug log.
bors bot
pushed a commit
that referenced
this issue
Dec 8, 2020
## Issue Addressed #2046 ## Proposed Changes The log was originally intended to verify the correct logic and ordering of events when scoring peers. The queued tasks can be structured in such a way that peers can be banned after they are disconnected. Therefore the error log is now downgraded to debug log.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
Your documentation says that if we see any ERRO messages we should open an issue. I found an ERRO message 😄
ERRO Banning a disconnected peer peer_id: 16Uiu2HAm26rS8jsaqG68htn1A4KHJ2avxVKcTuAjr8DAzdvpceq4, service: libp2pVersion
Docker v1.0.3
Present Behaviour
ERRO Banning a disconnected peer peer_id: 16Uiu2HAm26rS8jsaqG68htn1A4KHJ2avxVKcTuAjr8DAzdvpceq4, service: libp2pExpected Behaviour
🤷♂️
Steps to resolve
🤷♂️
The text was updated successfully, but these errors were encountered: