-
Notifications
You must be signed in to change notification settings - Fork 840
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
Hotfix 23.10.3-hotfix Log/Address Trielog rolling failure #6315
Merged
garyschulte
merged 4 commits into
hyperledger:release-23.10.3
from
garyschulte:bug/state-rolling-failure
Jan 7, 2024
Merged
Hotfix 23.10.3-hotfix Log/Address Trielog rolling failure #6315
garyschulte
merged 4 commits into
hyperledger:release-23.10.3
from
garyschulte:bug/state-rolling-failure
Jan 7, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
garyschulte
changed the title
raise log rolling failure loglevel to error from debug
Log/Address Trielog rolling failure
Dec 19, 2023
garyschulte
force-pushed
the
bug/state-rolling-failure
branch
2 times, most recently
from
December 22, 2023 04:51
928c7f5
to
a10ec47
Compare
raise log rolling failure loglevel to error from debug Signed-off-by: garyschulte <garyschulte@gmail.com>
Signed-off-by: Karim Taam <karim.t2am@gmail.com>
garyschulte
force-pushed
the
bug/state-rolling-failure
branch
from
January 6, 2024 22:48
4808dd9
to
c708891
Compare
garyschulte
changed the title
Log/Address Trielog rolling failure
Hotfix 23.10.4 Log/Address Trielog rolling failure
Jan 6, 2024
Signed-off-by: garyschulte <garyschulte@gmail.com>
jflo
approved these changes
Jan 6, 2024
Signed-off-by: garyschulte <garyschulte@gmail.com>
garyschulte
changed the title
Hotfix 23.10.4 Log/Address Trielog rolling failure
Hotfix 23.10.3-hotfix Log/Address Trielog rolling failure
Jan 6, 2024
jflo
pushed a commit
to jflo/besu
that referenced
this pull request
Jan 8, 2024
…r#6315) * trigger a BWS if we do not have a valid worldstate available during fcU raise log rolling failure loglevel to error from debug Signed-off-by: garyschulte <garyschulte@gmail.com> * fixing on selfdestruct Signed-off-by: Karim Taam <karim.t2am@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR description
Hotfix release to address production issue with bonsai state rolling and repeated selfdestruct, see also #6359
Fixed Issue(s)
#6357