erigon-pulse/consensus/bor/heimdall
Manav Darji 2d0e091a6e
eth, consensus/bor: handle 503 response from heimdall (#8364)
When a new feature (like for the upcoming `Aalborg` hard fork) for
Polygon hasn't kicked in (in heimdall), the endpoints of heimdall will
now return 503 (Service Unavailable) status code. This PR makes sure
that erigon handles that code separately and doesn't keep retying to
fetch info. It also acts as a notifier of the HF in erigon.

Similar reference PR in bor:
https://github.com/maticnetwork/bor/pull/1023
2023-10-04 13:43:07 +01:00
..
checkpoint Bor eth event flow (#8068) 2023-08-25 12:19:39 +01:00
milestone Get vote on hash (#8172) 2023-09-13 11:49:49 +01:00
span Bor mining benchmark (#8096) 2023-08-30 10:25:02 +01:00
client.go eth, consensus/bor: handle 503 response from heimdall (#8364) 2023-10-04 13:43:07 +01:00
heimall.go Bor break loop onrewind (#8302) 2023-09-27 13:17:54 +01:00
metrics.go Metrics label fixes (#8339) 2023-10-02 17:19:02 +01:00