-
Notifications
You must be signed in to change notification settings - Fork 122
feat(consume): add ExceptionMapper
support to the consume-engine simulator
#1416
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
Conversation
ExceptionMapper
support to the consume-engine simulator
I found there are some issue with refactored exception mapper. perhaps this can be address in here in this PR |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
waut the complexity of exception mapper is growing. I need to study python again.
f1c23d2
to
5427517
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Love this, few suggestions, also in #1464.
src/pytest_plugins/consume/hive_simulators/engine/test_via_engine.py
Outdated
Show resolved
Hide resolved
27845aa
to
ce47dbb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
…ype_requests_engine`
…only affects generated block tests)
35239db
to
4963923
Compare
🗒️ Description
Adds support of the exception mapper to consume-engine:
consume engine
now checks exceptions returned by the execution clients in their Engine API responses, specifically in thevalidationError
field of theengine_newPayloadVX
method.Exception mappers of all current mainnet clients have been added to the
ethereum_clis
library.The feature can be disabled by using
--disable-strict-exception-matching
for specific clients or forks.🔗 Related Issues
✅ Checklist
mkdocs serve
locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.