You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
#6004 fixes a bunch of known issues and Lighthouse is now able to slowly sync with peers, provided that peers are able to respond to data column by range requests. However it's not really reliable and gets "stuck" quite easily, so I suspect there are some other issues out there that haven't been discovered.
I don't have the logs with me now, however it's quite easy to reproduce:
Start a local testnet with the network_params_das_local.yaml config
Stop one Lighthouse node, and wait for 2-3 epochs to make sure it triggers range sync
Start the Lighthouse node, notice that sync gets stuck pretty quickly
This is now a bit harder to test due to #6108 and it might make sense to get to the bottom of that one first, or alternatively we could try to run a testnet with Prysm / Teku, whichever is able to serve the requests.
The text was updated successfully, but these errors were encountered:
Description
#6004 fixes a bunch of known issues and Lighthouse is now able to slowly sync with peers, provided that peers are able to respond to data column by range requests. However it's not really reliable and gets "stuck" quite easily, so I suspect there are some other issues out there that haven't been discovered.
I don't have the logs with me now, however it's quite easy to reproduce:
network_params_das_local.yaml
configThis is now a bit harder to test due to #6108 and it might make sense to get to the bottom of that one first, or alternatively we could try to run a testnet with Prysm / Teku, whichever is able to serve the requests.
The text was updated successfully, but these errors were encountered: