status-im
/
nimbus-eth2
mirror of https://github.com/status-im/nimbus-eth2.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

fcU on syncing newPayload syncing response (#3618)

This commit is contained in:
tersec 2022-05-08 07:09:46 +00:00 committed by GitHub
parent c6915ed3e0
commit 104cc3053f
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
beacon_chain/gossip_processing/block_processor.nim
View File

@ -453,7 +453,8 @@ proc runQueueProcessingLoop*(self: ref BlockProcessor) {.async.} =
blck.resfut.complete(Result[void, BlockError].err(BlockError.Invalid))
continue
if executionPayloadStatus == PayloadExecutionStatus.accepted and
if executionPayloadStatus in
[PayloadExecutionStatus.accepted, PayloadExecutionStatus.syncing] and
hasExecutionPayload:
# The EL client doesn't know here whether the payload is valid, because,
# for example, in Geth's case, its parent isn't known. When Geth logs an
@ -481,7 +482,7 @@ proc runQueueProcessingLoop*(self: ref BlockProcessor) {.async.} =
# cause a sync deadlock unless the EL can be convinced to sync back, or
# the CL is rather more open-endedly optimistic (potentially for entire
# weak subjectivity periods) than seems optimal.
debug "runQueueProcessingLoop: execution payload accepted",
debug "runQueueProcessingLoop: execution payload accepted or syncing",
executionPayloadStatus
await self.runForkchoiceUpdated(