Skip to content
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

chore(runway): cherry-pick fix: mark transactions as failed for cancelled / unknown smart transactions #12670

Merged
merged 1 commit into from
Dec 12, 2024

Conversation

runway-github[bot]
Copy link
Contributor

@runway-github runway-github bot commented Dec 12, 2024

Description

Resolves an issue with stuck transactions for some users who used smart
transactions, which was caused by having this
PR
in the
7.36.0 release even when it was marked for 7.37.0 by metamaskbot.

Related issues

Fixes:

Manual testing steps

  1. Cancelled transaction stuck thanks to super low gas settings
  2. All other submitted transactions afterwards as well with the
    invalid_nonce error.
  3. Upgrade to 7.37.1 and see all cancelled tx
  4. Try a new tx

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

  • I've manually tested the PR (e.g. pull and build branch, run the
    app, test code being changed).
  • I confirm that this PR addresses all acceptance criteria described
    in the ticket it closes and includes the necessary testing evidence such
    as recordings and or screenshots. cfb77b9

…lled / unknown smart transactions (#12664)

## **Description**
Resolves an issue with stuck transactions for some users who used smart
transactions, which was caused by having [this
PR](#12274) in the
7.36.0 release even when it was marked for 7.37.0 by metamaskbot.

## **Related issues**

Fixes:

## **Manual testing steps**

1. Cancelled transaction stuck thanks to super low gas settings
2. All other submitted transactions afterwards as well with the
invalid_nonce error.
3. Upgrade to 7.37.1 and see all cancelled tx
4. Try a new tx

## **Screenshots/Recordings**

<!-- If applicable, add screenshots and/or recordings to visualize the
before and after of your change. -->

### **Before**

https://consensys.slack.com/archives/C084S32G337/p1734034013370979

### **After**

https://consensys.slack.com/archives/C084S32G337/p1734039388196979

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Mobile
Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've completed the PR template to the best of my ability
- [ ] I’ve included tests if applicable
- [ ] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [ ] I’ve applied the right labels on the PR (see [labeling
guidelines](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [ ] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [ ] I confirm that this PR addresses all acceptance criteria described
in the ticket it closes and includes the necessary testing evidence such
as recordings and or screenshots.
@runway-github runway-github bot requested a review from a team as a code owner December 12, 2024 23:09
Copy link
Contributor

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.

@sethkfman
Copy link
Contributor

Bypass the audit:ci step as it seems to be an issue in Dev dependencies

@sethkfman sethkfman merged commit 0b4ddfd into release/7.37.1 Dec 12, 2024
31 of 38 checks passed
@sethkfman sethkfman deleted the runway-cherry-pick-7.37.1-1734044962 branch December 12, 2024 23:51
@github-actions github-actions bot locked and limited conversation to collaborators Dec 12, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants