Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: non-existent field access on error message #577

Merged
merged 2 commits into from
Apr 26, 2024

Conversation

MegaRedHand
Copy link
Contributor

@MegaRedHand MegaRedHand commented Apr 25, 2024

Fixes #576

Now it correctly results in the error message:

There was an error interpreting Starlark code 
Evaluation error: fail: Unsupported launcher 'foo', need one of 'lighthouse,lodestar,nimbus,prysm,teku,grandine'
        at [github.com/kurtosis-tech/ethereum-package/main.star:104:55]: run
        at [github.com/kurtosis-tech/ethereum-package/src/participant_network.star:166:34]: launch_participant_network
        at [github.com/kurtosis-tech/ethereum-package/src/cl/cl_launcher.star:106:17]: launch
        at [0:0]: fail

Error encountered running Starlark code.

@barnabasbusa
Copy link
Contributor

I’m sorry but why is “ Unsupported launcher 'foo', need one of 'lighthouse, lodestar, nimbus, prysm, teku, grandine'” not a sufficient error message? What CL client are you launching with your node?

@MegaRedHand
Copy link
Contributor Author

There's some context in #576. I was working on integrating https://github.com/lambdaclass/lambda_ethereum_consensus with this repo and found the bug when first adding our client to the args file: "Unsupported launcher ..." wasn't being printed, but an internal error because of outdated code (each client entry had a name attribute before, but they no longer do).

@barnabasbusa
Copy link
Contributor

Ah got it, good catch thanks!

@barnabasbusa barnabasbusa enabled auto-merge (squash) April 26, 2024 16:00
@barnabasbusa
Copy link
Contributor

Could you please update your branch with the latest main?

@MegaRedHand
Copy link
Contributor Author

Done!

@barnabasbusa barnabasbusa merged commit 8515d27 into ethpandaops:main Apr 26, 2024
9 checks passed
@MegaRedHand MegaRedHand deleted the fix-no-name-field branch April 26, 2024 17:42
barnabasbusa pushed a commit that referenced this pull request May 6, 2024
🤖 I have created a release *beep* *boop*
---


##
[3.0.0](2.2.0...3.0.0)
(2024-05-06)


### ⚠ BREAKING CHANGES

* add mev-rs relay/builder/boost
([#586](#586))
* upcoming file path change in kurtosis upstream
([#582](#582))

### Features

* add apache file server
([#581](#581))
([205256a](205256a))
* add enr/enode to apache
([#589](#589))
([b789e17](b789e17))
* add execution client urls to dora config
([#588](#588))
([2a20d5a](2a20d5a))
* add mev-rs relay/builder/boost
([#586](#586))
([525a8fb](525a8fb))
* Add peerdas support
([#591](#591))
([14296ca](14296ca))
* add snooper urls to assertoor config
([#571](#571))
([87f383f](87f383f))
* allow setting exit ip address
([#584](#584))
([aabc942](aabc942))


### Bug Fixes

* non-existent field access on error message
([#577](#577))
([8515d27](8515d27))
* participant redefining global flag
([#573](#573))
([9139f4b](9139f4b))
* path for shadowforks post kt update
([#585](#585))
([e0622a7](e0622a7))
* remove erigon's --chain parameter
([#575](#575))
([02b9c50](02b9c50))
* upcoming file path change in kurtosis upstream
([#582](#582))
([8d7c4f9](8d7c4f9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

"String has no .name field or method" when using unsupported CL client
2 participants