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

fix(cherry-pick): use PORTFOLIO_VIEW flag to determine chain polling #28578

Merged
merged 2 commits into from
Dec 2, 2024

Conversation

bergeron
Copy link
Contributor

Cherry picks #28504 to 12.8.0 so chains aren't polled unnecessarily

Updates the token price and detection hooks to only poll across chains
when `PORTFOLIO_VIEW` is set.

[![Open in GitHub
Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/MetaMask/metamask-extension/pull/28504?quickstart=1)

1. With `PORTFOLIO_VIEW=1`, requests should go to the price api across
all chains.
2. Without `PORTFOLIO_VIEW=1`, requests should go to the price api on
the current chain.

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

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

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

- [ ] 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.

- [ ] 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.
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.

@bergeron bergeron marked this pull request as ready for review November 20, 2024 21:28
@bergeron bergeron requested a review from a team as a code owner November 20, 2024 21:28
@metamaskbot metamaskbot added the INVALID-PR-TEMPLATE PR's body doesn't match template label Nov 20, 2024
@darkwing darkwing added the release-blocker This bug is blocking the next release label Nov 21, 2024
@hjetpoluru
Copy link
Contributor

@metamaskbot update-attributions

@metamaskbot
Copy link
Collaborator

No attributions changes

@metamaskbot
Copy link
Collaborator

Builds ready [a0baa5a]
Page Load Metrics (1957 ± 58 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint17682244195912861
domContentLoaded17602213192711455
load17692250195712158
domInteractive27232544421
backgroundConnect106929189
firstReactRender49291915627
getState452801005125
initialActions01000
loadScripts1303166514429747
setupStore6511095
uiStartup203829762268209101
Bundle size diffs
  • background: 0 Bytes (0.00%)
  • ui: 50 Bytes (0.00%)
  • common: 0 Bytes (0.00%)

@metamaskbot
Copy link
Collaborator

Builds ready [08b7902]
Page Load Metrics (1726 ± 46 ms)
PlatformPageMetricMin (ms)Max (ms)Average (ms)StandardDeviation (ms)MarginOfError (ms)
ChromeHomefirstPaint35419671658314151
domContentLoaded1583189217048842
load1594197317269646
domInteractive145334115
backgroundConnect999252311
firstReactRender462861006933
getState412931156029
initialActions01000
loadScripts1125142112577335
setupStore614721
uiStartup182427652092258124

@danjm danjm merged commit 8e074a6 into Version-v12.8.0 Dec 2, 2024
70 of 71 checks passed
@danjm danjm deleted the brian/v1280cherrypick branch December 2, 2024 21:26
@github-actions github-actions bot locked and limited conversation to collaborators Dec 2, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
INVALID-PR-TEMPLATE PR's body doesn't match template release-blocker This bug is blocking the next release team-assets
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants