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
non-fungible-nelson
added
P2
High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc))
TeamChupa
GH issues worked on by Chupacabara Team
TeamGroot
GH issues worked on by Groot Team
labels
Jun 22, 2023
non-fungible-nelson
added
P3
Medium (ex: JSON-RPC request not working with a specific client library due to loose spec assumtion)
and removed
P2
High (ex: Degrading performance issues, unexpected behavior of core features (DevP2P, syncing, etc))
labels
Jul 10, 2023
@non-fungible-nelson No, it's just in the backlog. Suspect it's less of an issue on mainnet compared to Sepolia. Also suspect playing this will make this a non-issue: #5687
Split out from #5411
Doesn't happen everytime, but easiest way to recreate is by simply restarting both clients together for an in-sync besu and nimbus pair.
Once the error is hit, it sometimes requires a restart to recover (in this case because it was cached in the bad block manager and re-requested).
besu7-restart.log
nimbus-engine7-restart.log
nimbus7-restart.log
The text was updated successfully, but these errors were encountered: