-
-
Notifications
You must be signed in to change notification settings - Fork 289
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
fix(validator): log api errors as warn
if node is syncing
#5467
Conversation
considering the log level if node is syncing, should we use |
Performance Report✔️ no performance regression detected 🚀🚀 Significant benchmark improvement detected
Full benchmark results
|
considering comments such as #4977 (comment), maybe we want to log "Node is syncing" as |
IMO a warn makes sense here. Once the node is synced, any "Node is syncing" message is likely not desired. Good to show a yellow light in that case. |
913a51d
to
b28d5a9
Compare
warn
if beacon node is syncing
warn
if beacon node is syncingwarn
if node is syncing
warn
if node is syncingwarn
if node is syncing
🎉 This PR is included in v1.9.0 🎉 |
Motivation
Logs mentioned in #5359 (comment) should not be shown as errors on the VC if beacon node is syncing.
Description
HttpError
is not thrown anymore, instead API client returns aApiClientResponse
lodestar/packages/api/src/utils/client/client.ts
Lines 81 to 85 in 913a51d
which will be handled by
ApiError.assert
and if not ok, will throwApiError
lodestar/packages/api/src/utils/client/httpClient.ts
Lines 42 to 46 in 913a51d
Before
After