In running the local devnet, we see:
t=2025-01-07T22:45:32+0000 lvl=warn msg="Event queue filled up, dropping oldest events" overflow=1
on op-nodes, scrolling by fairly regularly. Additionally, the op-supervisor logs show no events from nodes happening, only tracking new-L1 processing
t=2025-01-07T22:42:41+0000 lvl=warn msg="failed to poll L1 block" service=l1-processor label=finalized err="failed to fetch head header: not found"
t=2025-01-07T22:42:41+0000 lvl=warn msg="failed to poll L1 block" service=l1-processor label=finalized err="failed to fetch head header: not found"
t=2025-01-07T22:42:44+0000 lvl=warn msg="failed to poll L1 block" service=l1-processor label=finalized err="failed to fetch head header: not found"
t=2025-01-07T22:42:44+0000 lvl=warn msg="failed to poll L1 block" service=l1-processor label=finalized err="failed to fetch head header: not found"
t=2025-01-07T22:42:47+0000 lvl=info msg="Updated finalized L1" finalizedL1=0x4c51a6f89b19fc1dbc8678af6ea128b7dbe49edfa4c874388abf585d38519ca0:4
t=2025-01-07T22:42:47+0000 lvl=error msg="Failed to get finalized L1 block" chain=900200 err="could not find what was last derived from the finalized L1 block"
t=2025-01-07T22:42:47+0000 lvl=error msg="Failed to get finalized L1 block" chain=900201 err="could not find what was last derived from the finalized L1 block"
Looking into the message from the op-node takes us to this line:
|
evs.log.Warn("Event queue filled up, dropping oldest events", "overflow", overflow) |
Which only would trigger if the evs.sub was nil, meaning the supervisor doesn't have a subscription to the node events.
This is blocking correct functionality for interop and needs resolution.
Update
See R&D Discord, this has been identified to be an issue with the fallback to HTTP path:
https://discord.com/channels/1244729134312198194/1251353953107578970/1326601288431046718
In running the local devnet, we see:
on op-nodes, scrolling by fairly regularly. Additionally, the op-supervisor logs show no events from nodes happening, only tracking new-L1 processing
Looking into the message from the op-node takes us to this line:
optimism/op-service/rpc/stream.go
Line 270 in f65c549
Which only would trigger if the
evs.subwas nil, meaning the supervisor doesn't have a subscription to the node events.This is blocking correct functionality for interop and needs resolution.
Update
See R&D Discord, this has been identified to be an issue with the fallback to HTTP path:
https://discord.com/channels/1244729134312198194/1251353953107578970/1326601288431046718