Do not request SSE block_gossip from Grandine #4195
Description
🐞 Bug Report
Description
Grandine does not support SSE event block_gossip. We can check if the CL is Grandine to not subscribe to block_gossip, so that we get metrics for the rest, at least. Or we can divide the single call to multiple calls per event, but I don't fancy that, as I'm unaware how BNs might treat multiple streams from the same IP. Ideally this should be fixed on Grandine side, but until then we m
We subscribe to the following endpoints:
- head
- chain_reorg
- block_gossip
- block
Grandine supports the following:
- Attestation
- AttesterSlashing
- BlobSidecar
- Block
- BlsToExecutionChange
- ChainReorg
- ContributionAndProof
- DataColumnSidecar
- FinalizedCheckpoint
- Head
- PayloadAttributes
- ProposerSlashing
- VoluntaryExit
Has this worked before in a previous version?
No.
🔬 Minimal Reproduction
Run Charon with Grandine CL.
🔥 Error
14:08:38.838 WARN app-start Failed to start SSE client: handle SSE payload: invalid response status code {"addr": "http://172.16.0.14:4000", "url": "http://172.16.0.14:4000/eth/v1/events?topics=head&topics=chain_reorg&topics=block_gossip&topics=block", "status_code": 400}
app/sse/client.go:178 .connect
app/sse/client.go:103 .start
app/sse/listener.go:80 .func1
Issue on Grandine's github: grandinetech/grandine#541