NethermindEth / sedge

A one-click setup tool for PoS network/chain validators and nodes.
https://docs.sedge.nethermind.io
Apache License 2.0
157 stars 46 forks source link

Consensus client error with `--eth1-endpoints` flag #354

Closed mmsaki closed 8 months ago

mmsaki commented 9 months ago

Describe the bug docker-compose.yml script does not successfully start consensus client, I get the following error:

sedge-consensus-client  | error: Found argument '--eth1-endpoints' which wasn't expected, or isn't valid in this context
sedge-consensus-client  |   Did you mean --eth1?
sedge-consensus-client  | 
sedge-consensus-client  | USAGE:
sedge-consensus-client  |     lighthouse beacon_node --datadir <DIR> --disable-upnp --eth1 --execution-endpoint <EXECUTION-ENDPOINT> --execution-jwt <EXECUTION-JWT> --http-address <ADDRESS> --http-port <PORT> --network <network> --port <PORT> --target-peers <target-peers> <--http|--gui|--staking>

To Reproduce Steps to reproduce the behavior:

  1. Install latest version of Sedge
    curl -L https://github.com/NethermindEth/sedge/releases/download/v1.3.0/sedge-v1.3.0-darwin-amd64 --output sedge
    chmod +x ./sedge
    mv ./sedge /usr/local/bin/sedge
  2. Generate docker-compose.yml and .env files
    sedge generate full-node --latest --network sepolia
  3. Execute the setup
    docker compose up -d
  4. See error
    docker compose logs consensus

Expected behavior The Lighthouse client should log that it started successfully

Screenshots

Screenshot 2024-02-02 at 7 20 13 PM

Desktop (please complete the following information):

Additional context

mmsaki commented 9 months ago

Hello @stdevMac @cbermudez97. Could you please take a moment to review my pull request? I'd greatly appreciate your insights and feedback.

adriantpaez commented 8 months ago

Hi, @mmsaki thank you for the report and the open PR. This issue was fixed with the new version 1.3.1. Please try with the new version.

mmsaki commented 8 months ago

Hi, @mmsaki thank you for the report and the open PR. This issue was fixed with the new version 1.3.1. Please try with the new version.

Awesome, thanks, that was a quick fix!