Instructions
Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.
Problem
During the synchronization process, a grpc error occurred, causing the entire program to exit and unable to continue synchronization.
Steps to Reproduce
flow-evm-gateway[2342900]: {"level":"debug","version":"v1.4.2-experimental-sf.1","requested-cadence-height":111340190,"time":"2025-12-18T05:00:03Z","message":"using previous spork client"}
flow-evm-gateway[2342900]: {"level":"error","version":"v1.4.2-experimental-sf.1","component":"subscriber","error":"failed to get block events: client: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4965007 vs. 4194304)","time":"2025-12-18T05:00:03Z","message":"error backfilling spork"}
flow-evm-gateway[2342900]: {"level":"fatal","version":"v1.4.2-experimental-sf.1","component":"bootstrap-ingestion","engine":"*ingestion.Engine","error":"failure in event subscription with: failed to get block events: client: rpc error: code
= ResourceExhausted desc = grpc: received message larger than max (4965007 vs. 4194304)","time":"2025-12-18T05:00:03Z","message":"engine failed
to run"}
Main process exited, code=exited, status=1/FAILURE
Acceptance Criteria
Fixing this bug will allow the node to continue syncing.
Context
Currently, I am synchronizing blocks from scratch, but this issue causes the evm-gateway to exit abnormally, leading to the synchronization stopping at that block information.
Instructions
Please fill out the template below to the best of your ability and include a label indicating which tool/service you were working with when you encountered the problem.
Problem
During the synchronization process, a grpc error occurred, causing the entire program to exit and unable to continue synchronization.
Steps to Reproduce
flow-evm-gateway[2342900]: {"level":"debug","version":"v1.4.2-experimental-sf.1","requested-cadence-height":111340190,"time":"2025-12-18T05:00:03Z","message":"using previous spork client"}
flow-evm-gateway[2342900]: {"level":"error","version":"v1.4.2-experimental-sf.1","component":"subscriber","error":"failed to get block events: client: rpc error: code = ResourceExhausted desc = grpc: received message larger than max (4965007 vs. 4194304)","time":"2025-12-18T05:00:03Z","message":"error backfilling spork"}
flow-evm-gateway[2342900]: {"level":"fatal","version":"v1.4.2-experimental-sf.1","component":"bootstrap-ingestion","engine":"*ingestion.Engine","error":"failure in event subscription with: failed to get block events: client: rpc error: code
= ResourceExhausted desc = grpc: received message larger than max (4965007 vs. 4194304)","time":"2025-12-18T05:00:03Z","message":"engine failed
to run"}
Main process exited, code=exited, status=1/FAILURE
Acceptance Criteria
Fixing this bug will allow the node to continue syncing.
Context
Currently, I am synchronizing blocks from scratch, but this issue causes the evm-gateway to exit abnormally, leading to the synchronization stopping at that block information.