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

logs: Promote API calls errors to higher severirty logs (ERROR) #1783

Open
y0sher opened this issue Oct 9, 2024 · 1 comment
Open

logs: Promote API calls errors to higher severirty logs (ERROR) #1783

y0sher opened this issue Oct 9, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@y0sher
Copy link
Contributor

y0sher commented Oct 9, 2024

Description

Errors in interacting with external APIs like CL,EL nodes are something we want to present to the user right away when they happen.

Task

Make sure we print Error to the console whenever a call to EL/CL failed. Never silence them with Debug.

This might a bit harder said than done, some errors are swallowed by other errors, for example a processing of a message in consensus can trigger a call to CL which will result in an error, hence there was an error processing the message (which usually goes to debug).

@y0sher y0sher added the bug Something isn't working label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants
@y0sher and others