-
Notifications
You must be signed in to change notification settings - Fork 543
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
multiple nodes crashed #16397
Comments
deepthiskumar
added
bug
triage
mina-node
Issues related to all types of mina node
labels
Dec 4, 2024
georgeee
added a commit
that referenced
this issue
Dec 5, 2024
Dropped sequence was returned in reverse order, then concatenated to a sequence in straight order. This is part of a fix for issue #16397.
georgeee
added a commit
that referenced
this issue
Dec 5, 2024
1. Rewrite revalidate to enhance readability 2. Fix two similar issues originating from confusion between previous variable names `t` and `t'` ("Account no longer has permission to send" and "Current account nonce precedes first nonce in queue") 3. Fix the issue #16397 by ensuring removal from `applicable_by_fee` is done only for the previous head of queue.
georgeee
added a commit
that referenced
this issue
Dec 5, 2024
1. Rewrite revalidate to enhance readability 2. Fix two similar issues originating from confusion between previous variable names `t` and `t'` ("Account no longer has permission to send" and "Current account nonce precedes first nonce in queue") 3. Fix the issue #16397 by ensuring removal from `applicable_by_fee` is done only for the previous head of queue.
georgeee
added a commit
that referenced
this issue
Dec 5, 2024
Fix the issue #16397 by ensuring removal from `applicable_by_fee` is done only for the previous head of queue.
georgeee
added a commit
that referenced
this issue
Dec 5, 2024
Fix the issue #16397 by ensuring removal from `applicable_by_fee` is done only for the previous head of queue.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Preliminary Checks
Description
Multiple synced nodes crashed with the following exception
Restarting the nodes seem to have worked given block production isn't impacted
Steps to Reproduce
Still investigating
Expected Result
Nodes shouldn't crash
Actual Result
Crash
Daemon version
Seems like this is version independent as nodes with different versions have crashed
How frequently do you see this issue?
Rarely
What is the impact of this issue on your ability to run a node?
High
Status
Additional information
No response
The text was updated successfully, but these errors were encountered: