fix: test_event_blob_local_fork_recovery timeout #2278
Merged
Conversation
This file contains hidden or 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
halfprice
force-pushed
the
zhewu/event-blob-fork-test
branch
3 times, most recently
from
c673a56 to
b0b0930
Compare
halfprice
force-pushed
the
zhewu/event-blob-fork-test
branch
from
b0b0930 to
37d88c3
Compare
halfprice
changed the title
halfprice
force-pushed
the
zhewu/event-blob-fork-test
branch
7 times, most recently
from
79588c1 to
2448aec
Compare
halfprice
force-pushed
the
zhewu/event-blob-fork-test
branch
from
2448aec to
18c7a12
Compare
liquid-helium
approved these changes
Jul 3, 2025
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.
Description
With small checkpoints per event blob, reading latest event blob may fail due to that the certified events haven't been
processed yet. The workaround is to use large lag to trigger event blob catchup.
Test plan
How did you test the new or updated feature?
Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that
a user might notice and any actions they must take to implement updates. (Add release notes after the colon for each item)