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

feat: Add re-simulation feature (#12107) #12159

Merged
merged 3 commits into from
Nov 4, 2024
Merged

Conversation

OGPoyraz
Copy link
Member

@OGPoyraz OGPoyraz commented Nov 4, 2024

Description

Due to e2e failures this PR was reverted. Original PR here #12107

This PR cherry-picks #12073

Quality gate failures:

These are expected as we discussed - all those failures will be addressed in the https://github.com/MetaMask/MetaMask-planning/issues/3584

Hence adding skip-sonar-check label

Node version update:

It's a side effect of the bump to 7.0.1 of @metamask/rpc-errors.
https://github.com/MetaMask/rpc-errors/blob/main/package.json#L92

Related issues

Fixes: https://github.com/MetaMask/MetaMask-planning/issues/3380

Manual testing steps

Screenshots/Recordings

This feature already tested and released.
Please see the original picked PR for recording.

Before

After

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.

<!--
Please submit this PR as a draft initially.
Do not mark it as "Ready for review" until the template has been
completely filled out, and PR status checks have passed at least once.
-->

<!--
Write a short description of the changes included in this pull request,
also include relevant motivation and context. Have in mind the following
questions:
1. What is the reason for the change?
2. What is the improvement/solution?
-->

This PR cherry-picks
#12073

**Quality gate failures:**

These are expected as we discussed - all those failures will be
addressed in the
MetaMask/MetaMask-planning#3584

**Node version update:**

It's a side effect of the bump to `7.0.1` of` @metamask/rpc-errors`.
https://github.com/MetaMask/rpc-errors/blob/main/package.json#L92

Fixes: MetaMask/MetaMask-planning#3380

This feature already tested and released.
Please see the original picked PR for recording.

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

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

- [X] 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).
- [X] I've completed the PR template to the best of my ability
- [X] I’ve included tests if applicable
- [X] I’ve documented my code using [JSDoc](https://jsdoc.app/) format
if applicable
- [X] 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 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.

---------

Co-authored-by: Nico MASSART <NicolasMassart@users.noreply.github.com>
@OGPoyraz OGPoyraz added the team-confirmations Push issues to confirmations team label Nov 4, 2024
@OGPoyraz OGPoyraz requested review from a team as code owners November 4, 2024 09:57
@OGPoyraz OGPoyraz added No QA Needed Apply this label when your PR does not need any QA effort. Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 4, 2024
Copy link
Contributor

github-actions bot commented Nov 4, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 74d0595
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/484b3e97-cc90-447a-a5df-75d8f617e9b0

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@OGPoyraz OGPoyraz added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 4, 2024
Copy link
Contributor

github-actions bot commented Nov 4, 2024

https://bitrise.io/ Bitrise

🔄🔄🔄 pr_smoke_e2e_pipeline started on Bitrise...🔄🔄🔄

Commit hash: 9e6214b
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/9dcf986c-4cea-4ba9-a64f-867e035b83c7

Note

  • This comment will auto-update when build completes
  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

@OGPoyraz OGPoyraz added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 4, 2024
Copy link
Contributor

github-actions bot commented Nov 4, 2024

https://bitrise.io/ Bitrise

❌❌❌ pr_smoke_e2e_pipeline failed on Bitrise! ❌❌❌

Commit hash: 61762a5
Build link: https://app.bitrise.io/app/be69d4368ee7e86d/pipelines/50da4a79-e842-42c8-bac5-5ee68d7959cb

Note

  • You can kick off another pr_smoke_e2e_pipeline on Bitrise by removing and re-applying the Run Smoke E2E label on the pull request

Tip

  • Check the documentation if you have any doubts on how to understand the failure on bitrise

@OGPoyraz OGPoyraz added Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 4, 2024
Copy link

sonarqubecloud bot commented Nov 4, 2024

Quality Gate Failed Quality Gate failed

Failed conditions
41.1% Coverage on New Code (required ≥ 60%)
18.0% Duplication on New Code (required ≤ 10%)

See analysis details on SonarCloud

@OGPoyraz OGPoyraz added skip-sonar-cloud Only used for bypassing sonar cloud when failures are not relevant to the changes. Run Smoke E2E Triggers smoke e2e on Bitrise and removed Run Smoke E2E Triggers smoke e2e on Bitrise labels Nov 4, 2024
Copy link
Contributor

@sethkfman sethkfman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@OGPoyraz OGPoyraz added this pull request to the merge queue Nov 4, 2024
Merged via the queue into main with commit 385a577 Nov 4, 2024
76 of 78 checks passed
@OGPoyraz OGPoyraz deleted the feat/re-add-resimulation branch November 4, 2024 15:59
@github-actions github-actions bot locked and limited conversation to collaborators Nov 4, 2024
@metamaskbot metamaskbot added the release-7.36.0 Issue or pull request that will be included in release 7.36.0 label Nov 4, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
No QA Needed Apply this label when your PR does not need any QA effort. release-7.36.0 Issue or pull request that will be included in release 7.36.0 Run Smoke E2E Triggers smoke e2e on Bitrise skip-sonar-cloud Only used for bypassing sonar cloud when failures are not relevant to the changes. team-confirmations Push issues to confirmations team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants