Bump the kurtosis battery's ethereum-package pin to a launcher that passes beacon --bootnodes as a list
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- github-actions, rust
- Domain
- ci-cd, distributed-systems
Research direction
Read .github/workflows/kurtosis_assertoor.yml around line 35 and compare its ETHEREUM_PACKAGE_REF with the specified add-ethlambda commit, 1aec42f3fdd934ef0520f535630fe86eec30cfe0. Update the pin to that commit or a later commit from the branch, then check that the battery workflow passes on the pull request; done means beacon startup accepts the bootnodes and the run succeeds.
Written by the indexing model from the issue text.
Description
lambdaclass/ethlambda#825 makes ethlambda beacon --bootnodes a comma-separated list of ENRs and multiaddrs, and refuses a file path at startup.
The kurtosis + assertoor battery still pins a launcher that passes a file:
.github/workflows/kurtosis_assertoor.yml:35pinsETHEREUM_PACKAGE_REF: 67cb0e02dc0bd49ec9461cbf2ef7ac4a3232755f.- At that commit,
src/cl/ethlambda/ethlambda_launcher.starinlambdaclass/ethereum-packagewrites the resolved bootnodes to/tmp/ethlambda-bootnodes.txtand passes--bootnodes=/tmp/ethlambda-bootnodes.txt(lines 17-19 and 173-186).
So once lambdaclass/ethlambda#825 is on main, the battery's push runs fail at beacon startup whenever the launcher has a bootnode to pass.
Why it is not in lambdaclass/ethlambda#825. On pull_request the workflow tests ghcr.io/lambdaclass/ethlambda:unstable, which is main's image, not the PR's. A pin bump inside lambdaclass/ethlambda#825 would trigger a run that pairs the list-passing launcher with a binary that still reads a file, and fail. The bump only makes sense once that PR is on main and in unstable.
Fix. Set ETHEREUM_PACKAGE_REF to 1aec42f3fdd934ef0520f535630fe86eec30cfe0, or a later commit of the fork's add-ethlambda branch (head today: 860b338622). That commit is "refactor: pass ethlambda's bootnodes as a comma-separated list", and it passes --bootnodes=<comma-joined ENRs> through cl_shared.append_bootnode_arg. It is 16 commits ahead of 67cb0e02 (the builder wiring, reporting ethlambda's ENR and TCP multiaddr, the image tag among them), so the battery run on the bump's own PR is what checks those against main.
- Dominant language
- Rust
- Stars
- 86
- Forks
- 34
- Avg merge
- 9d 20h
- Merged PRs (30d)
- 77
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lambdaclass/ethlambda
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#777 · 1 reaction ·
Maintainers usually reply within 6 days
-
Run all gossip validation testsMay be free again @dicethedev claimed this 9 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
lambdaclass/ethlambda#725 · 2 comments ·
Maintainers usually reply within 6 days
-
Handle malformed DB dataMay be free again @dicethedev claimed this 115 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
lambdaclass/ethlambda#529 · 4 comments ·
Maintainers usually reply within 6 days
-
Document architectural choicesMay be free again @dicethedev claimed this 115 days ago, and no pull request is open. Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
lambdaclass/ethlambda#521 · 2 comments ·
Maintainers usually reply within 6 days
-
validator: accept a JSON produceBlockV3 answer, so proposals work behind blobberPossibly taken @MegaRedHand claimed this today. Open
Difficulty 3/5 1-2 days Newbie friendliness 30/100
lambdaclass/ethlambda#861 ·
Maintainers usually reply within 6 days
All issues in lambdaclass/ethlambda
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
antithesishq/bombadil#473 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
libracoder/kiri#669 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 5 days
-
autofixer: follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
tursodatabase/turso#12217 ·
Maintainers usually reply within 1 day
-
Declare the CMS schema library in the optional recipients extraPossibly taken A pull request linked to this issue is open or already merged. Openarea:python in-progress
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
yhay81/pyropdf#1005 · 2 comments ·
Maintainers usually reply within 1 day