-
Notifications
You must be signed in to change notification settings - Fork 70
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
Replay-blockchain option not purging state code cache #1406
Comments
I think it might make sense to silently remove the code cache if it's dirty. |
heifner
added a commit
that referenced
this issue
Oct 16, 2023
heifner
added a commit
that referenced
this issue
Oct 17, 2023
heifner
added a commit
that referenced
this issue
Oct 17, 2023
[4.0] Recreate EOS VM OC code cache if corrupt
heifner
added a commit
that referenced
this issue
Oct 17, 2023
heifner
added a commit
that referenced
this issue
Oct 17, 2023
[4.0 -> 5.0] Recreate EOS VM OC code cache if corrupt
heifner
added a commit
that referenced
this issue
Oct 17, 2023
heifner
added a commit
that referenced
this issue
Oct 17, 2023
[5.0 -> main] Recreate EOS VM OC code cache if corrupt
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When attempting to kick off a --replay-blockchain on a 3.2.4 node that crashed and left dirty db, I get the following error and it will not proceed:
Manually purging the state directory before the replay did resolve the issue (but ironically led me to the new "feature" where a missing state folder wont delete ship logs and errors out with generic cannot write to statehist logs error)
The text was updated successfully, but these errors were encountered: