-
Notifications
You must be signed in to change notification settings - Fork 44
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
Store transaction errors caught before broadcast #936
Conversation
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. Nice job with the optimizations while developing this. Left some comments but nothing major
} | ||
txm.lggr.Errorw("simulate: unrecognized error", logValues...) | ||
txm.lggr.Errorw("unrecognized error", logValues...) | ||
return Errored, errType |
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.
should this be fatally errored if it's simulation type?
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.
Good point, I'll check with CCIP to see what they think. I was sort of following the EVM TXM philosophy of keeping unknown errors retryable but surfacing it through logs. But we can tackle this with the later update for fatal errors
c299869
36e1adf
Quality Gate passedIssues Measures |
* Enabled TXM to store error statuses for transactions caught before broadcast * Addressed feedback * Removed id from finished tx metadata to reduce memory footprint * Updated logs
NONEVM-957
OnPrebroadcastError
method to the in-memory storage to directly put transactions into the errored state. Previously a transaction had to transition from another state to errored.FatallyErrored
status to classify specific Solana errors that should not be retried by plugin side code. Changes to parse and classify errors with this status will be introduced in a later update.