You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running in finalized mode, I keep getting error that particular block is not finalized, even though it is (according to beaconcha)
error: eth/v1/beacon/states/10631071/sync_committees?epoch=332222
error: {"execution_optimistic":false,"finalized":false,"data":{"validators":["1512778","1281133",......]]}}
error: true
error: false
info: Processing sync committee participation info
info: Successful reading validators registry file source.
error: getSyncCommitteeInfo: state finalized for epoch 332222 is not finalized
if I run in head mode, then this error is very similar, but
the error: getSyncCommitteeInfo: line is missing in the logs
the application doesn't scan 2-3 blocks backwards, just the head block (its expected I assume)
In the finalized mode, I won't see any metrics (I guess that's because it keeps getting errors) but in the head mode I do see some metrics though I'm not sure if they are accurate due to these errors.
I'm running nethermind EL, prysm CL. Do you know of any configuration to these clients which may cause them to respond with data which your application can't parse?
The text was updated successfully, but these errors were encountered:
When running in
finalized
mode, I keep getting error that particular block is not finalized, even though it is (according to beaconcha)if I run in
head
mode, then this error is very similar, buterror: getSyncCommitteeInfo:
line is missing in the logsIn the
finalized
mode, I won't see any metrics (I guess that's because it keeps getting errors) but in thehead
mode I do see some metrics though I'm not sure if they are accurate due to these errors.I'm running nethermind EL, prysm CL. Do you know of any configuration to these clients which may cause them to respond with data which your application can't parse?
The text was updated successfully, but these errors were encountered: