Skip to content

Conversation

@DeborahOlaboye
Copy link
Contributor

🗒️ Description

This PR refactors the ForkLoad.is_after_fork method to accept fork short names (e.g. "Paris", "Shanghai") instead of full module paths (e.g. "ethereum.forks.paris").

🔗 Related Issues or PRs

N/A.

Fixes #1424

✅ Checklist

  • All: Ran fast tox checks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:
    uvx --with=tox-uv tox -e lint,typecheck,spellcheck,markdownlint
  • All: PR title adheres to the repo standard - it will be used as the squash commit message and should start type(scope):.
  • All: Considered adding an entry to CHANGELOG.md.
  • All: Considered updating the online docs in the ./docs/ directory.
  • All: Set appropriate labels for the changes (only maintainers can apply labels).
  • Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.
  • Tests: For PRs implementing a missed test case, update the post-mortem document to add an entry the list.
  • Ported Tests: All converted JSON/YML tests from ethereum/tests or tests/static have been assigned @ported_from marker.

Cute Animal Picture

Put a link to a cute animal picture inside the parenthesis-->

Copy link
Contributor

@SamWilsn SamWilsn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You'll also want to change anywhere that calls is_after_fork, or else things will break.

return_value = False
for fork in self._forks:
if fork.name == target_fork_name:
short_name = fork.name.split(".")[-1]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should use short_name

@DeborahOlaboye
Copy link
Contributor Author

You'll also want to change anywhere that calls is_after_fork, or else things will break.

Okay, noted. Changes have now been applied. Kindly review.

@codecov-commenter
Copy link

⚠️ Please install the 'codecov app svg image' to ensure uploads and comments are reliably processed by Codecov.

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.08%. Comparing base (78240b6) to head (e450113).
❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files
@@             Coverage Diff              @@
##           forks/osaka    #1448   +/-   ##
============================================
  Coverage        86.08%   86.08%           
============================================
  Files              743      743           
  Lines            44072    44072           
  Branches          3891     3891           
============================================
  Hits             37938    37938           
  Misses            5656     5656           
  Partials           478      478           
Flag Coverage Δ
unittests 86.08% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@SamWilsn SamWilsn merged commit 7315523 into ethereum:forks/osaka Oct 3, 2025
8 checks passed
danceratopz pushed a commit to danceratopz/execution-specs that referenced this pull request Oct 22, 2025
…thereum#1448)

Convert all EOF validation tests for EIP-4200 (relative jumps)
to use `max_stack_increase`. The conversion here is simple because
all these tests use the code section 0 and therefore
`max_stack_increase` is equivalent to `max_stack_height`.
SamWilsn pushed a commit that referenced this pull request Dec 9, 2025
…1448)

Convert all EOF validation tests for EIP-4200 (relative jumps)
to use `max_stack_increase`. The conversion here is simple because
all these tests use the code section 0 and therefore
`max_stack_increase` is equivalent to `max_stack_height`.
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.

refactor(tool): Change is_after_fork method

3 participants