Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[first-issue] improve networking logging when neard is restarted #9565

Open
wacban opened this issue Sep 22, 2023 · 0 comments
Open

[first-issue] improve networking logging when neard is restarted #9565

wacban opened this issue Sep 22, 2023 · 0 comments
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

Comments

@wacban
Copy link
Contributor

wacban commented Sep 22, 2023

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.

@wacban wacban added 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 labels Sep 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
Development

No branches or pull requests

1 participant