-
Notifications
You must be signed in to change notification settings - Fork 724
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
Deposit contract finalization fails after checkpoint sync without deposit snapshot #3707
Labels
bug
Something isn't working
Comments
michaelsproul
added
bug
Something isn't working
v3.3.0
Minor release following v3.2.0
labels
Nov 9, 2022
bors bot
pushed a commit
that referenced
this issue
Nov 21, 2022
## Issue Addressed Partially addresses #3707 ## Proposed Changes Drop `ERRO` log to `WARN` until we identify the exact conditions that lead to this case. Add a message which hopefully reassures users who only see this log once 😅 Add the block hash to the error message in case it will prove useful in debugging the root cause.
In v3.3.0 this will present as |
michaelsproul
added
v3.4.0
Minor release following v3.3.0
and removed
v3.3.0
Minor release following v3.2.0
labels
Nov 24, 2022
macladson
pushed a commit
to macladson/lighthouse
that referenced
this issue
Jan 5, 2023
## Issue Addressed Partially addresses sigp#3707 ## Proposed Changes Drop `ERRO` log to `WARN` until we identify the exact conditions that lead to this case. Add a message which hopefully reassures users who only see this log once 😅 Add the block hash to the error message in case it will prove useful in debugging the root cause.
paulhauner
added
v3.5.0
Minor release circa Q1 2023
and removed
v3.4.0
Minor release following v3.3.0
labels
Jan 9, 2023
I've pushed this to v3.5.0, LMK if this is an issue @michaelsproul |
Woodpile37
pushed a commit
to Woodpile37/lighthouse
that referenced
this issue
Jan 6, 2024
## Issue Addressed Partially addresses sigp#3707 ## Proposed Changes Drop `ERRO` log to `WARN` until we identify the exact conditions that lead to this case. Add a message which hopefully reassures users who only see this log once 😅 Add the block hash to the error message in case it will prove useful in debugging the root cause.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After checkpoint syncing my node from a public endpoint without
deposit_snapshot
support, I got an error log upon trying to finalize the cache:I think this is because my node hadn't caught up to the finalized eth1 data. It recovered gracefully once it did, but I think it would be nice to avoid the
ERRO
log. We could just change it to aWARN
if we think that it's too hard to differentiate the types of failure here. It should be quite infrequent anyway.Version
v3.2.1 with #2915
The text was updated successfully, but these errors were encountered: