-
Notifications
You must be signed in to change notification settings - Fork 69
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
When setting block-log-retain-blocks = 0 get lots of unlinkable blocks errors #2006
Closed
Comments
Reproduced on eos mainnet by starting from a June snapshot. |
Not reproducible on 4.0 during my testing. |
heifner
added a commit
that referenced
this issue
Dec 20, 2023
heifner
added a commit
that referenced
this issue
Dec 20, 2023
[5.0] Fix unlinkable block exceptions when block-log-retain-blocks = 0
heifner
added a commit
that referenced
this issue
Dec 20, 2023
heifner
added a commit
that referenced
this issue
Dec 20, 2023
[5.0 -> main] Fix unlinkable block exceptions when block-log-retain-blocks = 0
heifner
added a commit
that referenced
this issue
Dec 20, 2023
[5.0] Test: Check for unlinkable blocks while syncing
heifner
added a commit
that referenced
this issue
Dec 21, 2023
heifner
added a commit
that referenced
this issue
Dec 21, 2023
[5.0] Test: Check for unlinkable blocks while syncing - 2
heifner
added a commit
that referenced
this issue
Dec 21, 2023
…nc-main [5.0 -> main] Test: Check for unlinkable blocks while syncing
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In 5.0.0-rc3, when setting
block-log-retain-blocks = 0
get lots of unlinkable blocks errors. This worked fine in 3.2. Not tested in 4.0Easy to reproduce on a heavy blockchain like wax, when starting from a snapshot. Seen on other lighter chains as well, even when starting from up-to-date.
The text was updated successfully, but these errors were encountered: