-
Notifications
You must be signed in to change notification settings - Fork 781
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
Stuck lookup reports #5833
Comments
ho-h-bn-toga - 0x4449a0eb35516c34a10fe21ded0467131674b4ea5dad86465305ba32e3ca0baf
This block has 2 blobs
Stuck cause
Fix TBD Same status and root cause for this other incidents:
|
This was referenced May 24, 2024
A specific subcase documented here: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Collection of investigations of
Notify the devs, a sync lookup is stuck
events:ho-h-bn-toga - 0x9bf61d9f31473fc8a9a91891b9601f9c6a04450ebe55bbde0a083c60a0b36997
Lookup
0x9bf61d9f31473fc8a9a91891b9601f9c6a04450ebe55bbde0a083c60a0b36997
^ this block has 1 blob
Stuck cause:
The new lookup 56 is created while the block is in the processing cache,
block_lookup_request
returnsPending
. However, the block is processing from a previous RPC lookup. The event that is returned from processing gets ignored because it's for a previous ID.Fix
TBD
The text was updated successfully, but these errors were encountered: