-
Notifications
You must be signed in to change notification settings - Fork 2.2k
fix: add bundle and transaction context to call_many errors #18127
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
mattsse
left a comment
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.
this is indeed more helpful,
but this shouldnt be converted to an internal error, can we instead introduce a new error variant for this that wraps the error and adds a message as config?
|
@mattsse GM, Would please check the new change since last feedback? |
|
@mattsse Hi the 1.7.0 seems to be a long time ago.. maybe the CI block this for merge, All ci fixed now. |
mattsse
left a comment
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.
useful context imo
mattsse
left a comment
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.
useful context imo
…xyz#18127) Co-authored-by: Matthias Seitz <[email protected]>
…xyz#18127) Co-authored-by: Matthias Seitz <[email protected]>
When
eth_callManyfails during transaction preparation or execution, the error message doesn't indicate which specific bundle or transaction caused the failure. This makes debugging difficult when processing multiple bundles with multiple transactions each.Before:
insufficient funds for gas * price + valueAfter:
call execution error at bundle 1, tx 1: insufficient funds for gas * price + value