-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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: get supportedChains
to avoid blocking the confirmation process
#28313
Merged
+271
−293
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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. |
vinistevam
force-pushed
the
fix/supported-chains-blocks-sendflow
branch
from
November 6, 2024 10:13
8e1be2a
to
01585d0
Compare
vinistevam
force-pushed
the
fix/supported-chains-blocks-sendflow
branch
from
November 6, 2024 11:13
29aa3cb
to
df1e50c
Compare
vinistevam
force-pushed
the
fix/supported-chains-blocks-sendflow
branch
from
November 6, 2024 14:30
505d22f
to
071863b
Compare
Builds ready [48d0796]
Page Load Metrics (1891 ± 63 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [6d98182]
Page Load Metrics (2126 ± 97 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Overall looks good 🙌 In summary:
fix-blocking-reqs-send.mp4blocking-all-api-reqs-malicious.mp4 |
matthewwalsh0
requested changes
Nov 8, 2024
Builds ready [f0ad166]
Page Load Metrics (1892 ± 94 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
vinistevam
force-pushed
the
fix/supported-chains-blocks-sendflow
branch
from
November 9, 2024 13:09
f0ad166
to
bcca3d4
Compare
Builds ready [bcca3d4]
Page Load Metrics (1863 ± 89 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
jpuri
reviewed
Nov 11, 2024
matthewwalsh0
requested changes
Nov 11, 2024
matthewwalsh0
requested changes
Nov 11, 2024
vinistevam
force-pushed
the
fix/supported-chains-blocks-sendflow
branch
from
November 12, 2024 00:16
3697061
to
391feea
Compare
Builds ready [391feea]
Page Load Metrics (1899 ± 115 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Builds ready [3fe3280]
Page Load Metrics (2028 ± 87 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
<!-- 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. --> ## **Description** <!-- 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? --> [![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28418?quickstart=1) ## **Related issues** Fixes: ## **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 Contributor Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask Extension Coding Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.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-extension/blob/develop/.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.
matthewwalsh0
approved these changes
Nov 12, 2024
Builds ready [d850354]
Page Load Metrics (1717 ± 60 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
pedronfigueiredo
approved these changes
Nov 12, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Nov 12, 2024
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
Nov 12, 2024
metamaskbot
added
the
release-12.8.0
Issue or pull request that will be included in release 12.8.0
label
Nov 12, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
release-12.8.0
Issue or pull request that will be included in release 12.8.0
team-confirmations
Push issues to confirmations team
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR addresses the blocking behaviour in the confirmation process caused by the synchronous
supportedChains
check. Previously, the Send flow was halted until a response from thesecurity-alerts.api.cx.metamask.io
API was received. This created delays and negatively impacted the user experience, especially when the API response was slow.Key Changes:
Asynchronous Chain Validation: The
supportedChains
check is now performed asynchronously within the non-awaitedvalidateRequestWithPPOM
function. This ensures that the Send flow is not blocked while waiting for the API response.Introduction of CheckingChain Result Type: A new result type,
CheckingChain
, is introduced to represent the intermediate state before a definitive result is obtained. This state is used before theloading
status in both middleware and transaction utility functions.Related issues
Fixes: #28255 #28257
Manual testing steps
security-alerts.api.cx.metamask.io
Screenshots/Recordings
supported-chains-.webm
unsupported-chains.webm
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist