chores(consume): rename --bin flag of consume direct to --evm-bin to be consistent with fill's --evm-bin#2548
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## forks/amsterdam #2548 +/- ##
================================================
Coverage 86.35% 86.35%
================================================
Files 599 599
Lines 36904 36904
Branches 3771 3771
================================================
Hits 31868 31868
Misses 4485 4485
Partials 551 551
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
danceratopz
left a comment
There was a problem hiding this comment.
@felix314159 could you pull the cli flag change out into a dedicated PR (but see comment below), these changes are too orthogonal respectively contentious for a single PR imo.
About the flag change, I know the difference is mildly annoying, but this was a deliberate choice in consume as it can run tests that are don't strictly require an EVM binary. I must admit that the only example I can think of right now is eoftest which validated EOF bytecode without EVM execution. But I think I'd still rather keep it more general at --bin. If anything, fill's --evm-bin flag is slightly too verbose (it was too tightly coupled to passing geth's evm binary). I think would prefer to leave consume as-is, but you could add an additional a --bin alias for --evm-bin to fill if helps things feel more consistent?
danceratopz
left a comment
There was a problem hiding this comment.
Here's a review on the ethereum-spec-evm-resolver to ethereum-spec-evm fix-ups! Good catch!
|
|
||
| CURRENT_FOLDER = Path(realpath(__file__)).parent | ||
| FIXTURES_ROOT = CURRENT_FOLDER / "fixtures" | ||
| DEFAULT_EVM_T8N_BINARY_NAME = "ethereum-spec-evm-resolver" |
There was a problem hiding this comment.
Def worth cleaning up here, but I think we could completely remove this global and the test that uses it. The test is marked as skip, so essentially deadcode atm. The other option is to parametrize the test with other detected t8n tools? But I consider that overkill as we're not missing this test right now and it's implicitly system-tested via the benchchmark tests which use evmone-t8n/geth.
| This is required in order for fill to locate the ethereum-spec-evm-resolver | ||
| "binary" (entrypoint) when being executed using pytester. | ||
| This is required so pytester-based invocations can locate the | ||
| execution-specs transition tool entrypoint while running in tests. |
There was a problem hiding this comment.
turbo nit sorry
| execution-specs transition tool entrypoint while running in tests. | |
| `ethereum-spec-evm t8n` entrypoint while running in tests. |
There was a problem hiding this comment.
This is the skip I mean. I think we can entirely remove this test.
|
Just to add that I didn't manage to finish reviewing the main part, but it looks to make makes sense. I'd like to check whether geth's behavior changed here (intentionally)? Will come back to this. Regarding this, assuming this is the main feature of this PR, wouldn't the title be: |
|
the PR started with me wanting to change the |
Nothing changed on the geth side. I'm just surprised that we didn't spot this earlier. Perhaps we had a regression on the testing framework side. Thanks for finding and fixing it! |
…direct), remove stale references to ethereum-spec-evm-resolver
Co-authored-by: danceratopz <danceratopz@gmail.com>
89330b0 to
9343545
Compare
consume direct for geth + chores--bin flag of consume direct to --evm-bin to be consistent with fill's --evm-bin
|
I moved the geth fix to a different PR, so this review should be straight-forward (just ignore my branch name) |
spencer-tb
left a comment
There was a problem hiding this comment.
I like the change. LGTM! Approved the geth tx reciepts PR too.
|
@danceratopz can you 'resolve the threads' and make the 'requested change' thing disappear if you agree with how i implemented them? |
As per #2548 (review) above, I would still prefer to:
@felix314159 wdyt? |
In hindsight, I think this is the way. |
|
I would like there to be one flag, and I don't care whether it is |
|
Happy to use |
Yup, I echo this. I don't see the need to make a sudden breaking change for everyone. So alias, with deprecation message if you consider important (for me leaving an alias indefinitely is also ok). Alongside the doc changes, we should also fix-up CI. |
🗒️ Description
Renames
consume direct's--binflag to--evm-binso the binary flag is consistent withfill --evm-bin, and it removes stale references toethereum-spec-evm-resolvernow that the weld is completed.🔗 Related Issues or PRs
N/A.
✅ Checklist
toxchecks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx tox -e statictype(scope):.mkdocs servelocally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.@ported_frommarker.Cute Animal Picture