-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
fix: mark transactions as failed for cancelled / unknown smart transactions #12664
Conversation
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Bitrise❌❌❌ Commit hash: e8bd386 Note
Tip
|
8a5bb41
to
4922c55
Compare
Bitrise❌❌❌ Commit hash: ce8842e Note
Tip
|
…ctions (WIP) Code cleanup, update tests Disable a lint line Linting
ce8842e
to
1b71a0e
Compare
Bitrise✅✅✅ Commit hash: 1b71a0e Note
|
Quality Gate passedIssues Measures |
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.
Code looks fine to me. Would not recommend using any
type though. Would be good to have an approval from someone from transactions team too
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
} | ||
|
||
const transactionControllerState = | ||
state.engine.backgroundState.TransactionController; |
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.
Minor, could we assign these at the start to avoid the duplicate property chains?
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.
Thanks for feedback, Matt! I just copied the 039.ts TransactionController migration and slightly modified it to get this fix out of the door asap. Will keep your comments in mind for another migration.
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.
FYI, I've resolved your feedback in a follow up PR: #12694
Description
Resolves an issue with stuck transactions for some users who used smart transactions, which was mainly caused by mistakenly believing that this PR was in the 7.37.0 release based on the label from metamaskbot, when it was in fact in the 7.36.0 release.
Related issues
Fixes:
Manual testing steps
Screenshots/Recordings
Before
https://consensys.slack.com/archives/C084S32G337/p1734034013370979
After
https://consensys.slack.com/archives/C084S32G337/p1734039388196979
Pre-merge author checklist
Pre-merge reviewer checklist