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
Hello, I'm having trouble starting the beacon client in my local environment. I checked the syncing status by calling /eth/v1/node/syncing, and it appears to remain stuck in the synchronizing process whenever there are no blocks to sync. I tested version 5.2.1, and it functions correctly in the local environment. In the Holeskey environment, version 5.3.0 works without any issues. The problem only occurs with version 5.3.0 in my local setup. I would appreciate any ideas or suggestions on this. Thank you in advance!
I anticipate receiving the following response, as version 5.2.1 would provide. curl -X 'GET' 'http://localhost:3500/eth/v1/node/syncing' -H 'accept: application/json'
AFAIK only the /eth/v1/node/syncing API is affected, so it is only a cosmetic regression. If you run a Lighthouse validator client it will ignore this and continue to produce blocks and attestations.
Description
Hello, I'm having trouble starting the beacon client in my local environment. I checked the syncing status by calling
/eth/v1/node/syncing
, and it appears to remain stuck in the synchronizing process whenever there are no blocks to sync. I tested version 5.2.1, and it functions correctly in the local environment. In the Holeskey environment, version 5.3.0 works without any issues. The problem only occurs with version 5.3.0 in my local setup. I would appreciate any ideas or suggestions on this. Thank you in advance!Version
v5.3.0
Present Behaviour
curl -X 'GET' 'http://localhost:3500/eth/v1/node/syncing' -H 'accept: application/json'
Expected Behaviour
I anticipate receiving the following response, as version 5.2.1 would provide.
curl -X 'GET' 'http://localhost:3500/eth/v1/node/syncing' -H 'accept: application/json'
The text was updated successfully, but these errors were encountered: