You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was reproduced a couple of times in Sepolia, when the node is running, specially on node startup. Here are some logs, they don't show a lot but the thing is the node keeps waiting there without doing anything more, I will assume this has to do with peer discovery, but we need to check if thats the case:
INFO 17:43:40.228 [Optimistic sync] Performing optimistic sync between slots 5963489 and 5963618, for a total of 130 slots.
INFO 17:43:40.228 [Optimistic sync] Sending request for slots 5963489 to 5963504 (request size = 16).
INFO 17:43:40.228 [Optimistic sync] Sending request for slots 5963505 to 5963520 (request size = 16).
INFO 17:43:40.228 [Optimistic sync] Sending request for slots 5963521 to 5963536 (request size = 16).
INFO 17:43:40.228 [Optimistic sync] Sending request for slots 5963537 to 5963552 (request size = 16).
INFO 17:43:40.229 [Optimistic sync] Sending request for slots 5963553 to 5963568 (request size = 16).
INFO 17:43:40.229 [Optimistic sync] Sending request for slots 5963569 to 5963584 (request size = 16).
INFO 17:43:40.229 [Optimistic sync] Sending request for slots 5963585 to 5963600 (request size = 16).
INFO 17:43:40.229 [Optimistic sync] Sending request for slots 5963601 to 5963616 (request size = 16).
INFO 17:43:40.229 [Optimistic sync] Sending request for slots 5963617 to 5963618 (request size = 2).
INFO 17:43:40.229 [Optimistic Sync] Blocks remaining: 130
The text was updated successfully, but these errors were encountered:
rodrigo-o
added
bug
Something isn't working
P1
This is a MUST for this milestone. It's a main feature, or blocking other main features.
labels
Sep 26, 2024
This was reproduced a couple of times in Sepolia, when the node is running, specially on node startup. Here are some logs, they don't show a lot but the thing is the node keeps waiting there without doing anything more, I will assume this has to do with peer discovery, but we need to check if thats the case:
The text was updated successfully, but these errors were encountered: