-
Notifications
You must be signed in to change notification settings - Fork 280
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
Unexpected exception thrown for java.lang.NullPointerException #1713
Comments
Thanks for reporting this, sorry for the delay in getting back to you. The sync will be "completing" early because Teku doesn't yet support snappy compression for gossip so isn't receiving any gossiped blocks. So we sync up to the status peers reported when they first connected and stop, thinking that we've got all the available blocks. #1722 will help with that, though there appears to be something else preventing us from getting gossip just yet. If you're not running any validators, #1724 may wind up silencing the errors but the underlying issue appears to be that the head block root doesn't appear to have a matching state in the store. That shouldn't be possible and we're currently investigating how it happens. |
Looks like these errors are related to: #1730 Working on a comprehensive fix. |
Fixed by: #1734 |
Description
On Schlesi, the client tells me to report the following exception after the sync seemingly completed:
Steps to Reproduce (Bug)
Expected behavior:
Run Smoothly.
Actual behavior:
Runtime Exception:
Note how finalized epoch is lacking behind (even though the chain is finalized at 1138) and the blocks are empty (even though they aren't).
Frequency:
1 - Only did one full sync so far.
Versions (Add all that apply)
The text was updated successfully, but these errors were encountered: