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
While restarting the node after a long run using gnolang start, I encountered a panic error (twice), related to fetching height 5063, which seems not to be present in the WAL file. This issue appears to occur when waking up the system from sleep mode on my laptop after an extended period of inactivity.
According to @ajnavarro's answer on Slack, the problem might occur when saving height data into both the key/value database and the WAL file. There's suspicion of missing flush calls in various parts of the code.
Unexpected Panic Error When Fetching Height
Description
While restarting the node after a long run using
gnolang start
, I encountered a panic error (twice), related to fetching height 5063, which seems not to be present in the WAL file. This issue appears to occur when waking up the system from sleep mode on my laptop after an extended period of inactivity.According to @ajnavarro's answer on Slack, the problem might occur when saving height data into both the key/value database and the WAL file. There's suspicion of missing flush calls in various parts of the code.
Your environment
Steps to reproduce
Expected behavior
The application should fetch height information without causing a panic error.
Actual behavior
A panic error occurs, with the message "panic: should not happen."
Logs
The text was updated successfully, but these errors were encountered: