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: cherry-pick #8605 #8609

Merged
merged 1 commit into from
Feb 16, 2024
Merged

Conversation

github-actions[bot]
Copy link
Contributor

This PR cherry-picks #8605

…8605)

## **Description**
A recent geth update and how a eth_createAccessList request is handled
when passed certain variables, created an incompatibility with ppom
causing it to fail with `gasPrice must be non-zero after london fork,
data: None)`.

The incompatibility of ppom and the latest changes in geth is handled in
v1.4.1 of ppom_release.

## **Related issues**

Fixes: #8589

## **Manual testing steps**

1. Go to this page...
2.
3.

## **Screenshots/Recordings**

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

### **Before**

<!-- [screenshots/recordings] -->

### **After**

<!-- [screenshots/recordings] -->

## **Pre-merge author checklist**

- [ ] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-mobile/blob/main/.github/guidelines/CODING_GUIDELINES.md).
- [ ] I've clearly explained what problem this PR is solving and how it
is solved.
- [ ] I've linked related issues
- [ ] I've included manual testing steps
- [ ] I've included screenshots/recordings if applicable
- [ ] 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.
- [ ] I’ve properly set the pull request status:
  - [ ] In case it's not yet "ready for review", I've set it to "draft".
- [ ] In case it's "ready for review", I've changed it from "draft" to
"non-draft".

## **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.
@NicolasMassart NicolasMassart marked this pull request as ready for review February 16, 2024 16:26
@NicolasMassart NicolasMassart requested a review from a team as a code owner February 16, 2024 16:26
@github-actions github-actions bot added the Run Smoke E2E Triggers smoke e2e on Bitrise label Feb 16, 2024
Copy link
Contributor Author

E2E test started on Bitrise: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/a399f5fd-dc37-4bb9-ad95-4e1e607ad39f
You can also kick off another Bitrise E2E smoke test by removing and re-applying the (Run Smoke E2E) label

@NicolasMassart NicolasMassart merged commit 503140f into release/7.16.0 Feb 16, 2024
4 checks passed
@NicolasMassart NicolasMassart deleted the chore/cherry-pick-8605 branch February 16, 2024 16:33
@github-actions github-actions bot locked and limited conversation to collaborators Feb 16, 2024
@metamaskbot metamaskbot added the release-7.16.0 Issue or pull request that will be included in release 7.16.0 label Feb 16, 2024
@metamaskbot
Copy link
Collaborator

No release label on PR. Adding release label release-7.16.0 on PR, as PR was cherry-picked in branch 7.16.0.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
release-7.16.0 Issue or pull request that will be included in release 7.16.0 Run Smoke E2E Triggers smoke e2e on Bitrise
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants