[first-issue] improve networking logging when neard is restarted #9565
Labels
C-good-first-issue
Category: issues that are self-contained and easy for newcomers to work on.
T-core
Team: issues relevant to the core team
When the neard process is restarted on a node in production network there are a number of warnings and errors that show up before the process stablizes and establishes itself in the network.
One error in particular is the "Failed to connect" error which is annoying because it contains newlines and really stands out while being harmless.
The goal of this issue is to change the error message to be in a single line.
An optional extension would be to list the remaining errors, evaluate if they are legitimate and file follow up issues to fix them.
The text was updated successfully, but these errors were encountered: