Skip to content

Conversation

@runway-github
Copy link
Contributor

@runway-github runway-github bot commented Nov 10, 2025

Description

In this PR, Downgrades Rive file load errors to warnings and removes
redundant error logging in social backup restore, adding a new
@rive-app/canvas patch reference.

Open in GitHub Codespaces

Changelog

CHANGELOG entry: null

Related issues

Fixes:

Manual testing steps

  1. Go to this page...

Screenshots/Recordings

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.

Note

Downgrades Rive file load errors to warnings, removes redundant error logging in social backup restore, and adds a new @rive-app/canvas patch reference.

  • Rive canvas patch (.yarn/patches/@rive-app-canvas-patch-03752f0c3b.patch):
    • Convert RiveFile load errors from throw/fireLoadError to console.warn and return early when missing src/buffer in rive.js.
  • Social backup restore logging:
    • Remove redundant log.error in restoreSocialBackupAndGetSeedPhrase catch blocks in app/scripts/metamask-controller.js and ui/store/actions.ts.
  • Dependencies/patch refs:
    • Update package.json and yarn.lock to include the new @rive-app/canvas patch chain.

Written by Cursor Bugbot for commit fb7ed7c. This will update automatically on new commits. Configure here.

7686502

…try cp-13.9.0 (#37649)

<!--
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?
-->

In this PR, Downgrades Rive file load errors to warnings and removes
redundant error logging in social backup restore, adding a new
@rive-app/canvas patch reference.

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

## **Changelog**

<!--
If this PR is not End-User-Facing and should not show up in the
CHANGELOG, you can choose to either:
1. Write `CHANGELOG entry: null`
2. Label with `no-changelog`

If this PR is End-User-Facing, please write a short User-Facing
description in the past tense like:
`CHANGELOG entry: Added a new tab for users to see their NFTs`
`CHANGELOG entry: Fixed a bug that was causing some NFTs to flicker`

(This helps the Release Engineer do their job more quickly and
accurately)
-->

CHANGELOG entry: null

## **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**

- [x] I've followed [MetaMask Contributor
Docs](https://github.com/MetaMask/contributor-docs) and [MetaMask
Extension Coding
Standards](https://github.com/MetaMask/metamask-extension/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-extension/blob/main/.github/guidelines/LABELING_GUIDELINES.md)).
Not required for external contributors.

## **Pre-merge reviewer checklist**

- [x] I've manually tested the PR (e.g. pull and build branch, run the
app, test code being changed).
- [x] 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.

<!-- CURSOR_SUMMARY -->
---

> [!NOTE]
> Downgrades Rive file load errors to warnings and removes redundant
error logging in social backup restore, adding a new @rive-app/canvas
patch reference.
> 
> - **Animations (@rive-app/canvas patch)**:
> - Suppress hard failures in `rive.js` by commenting out
`fireLoadError`/`throw` paths and using `console.warn`; add early return
when missing source.
> - **Error Logging**:
> - Remove `log.error` lines in `restoreSocialBackupAndGetSeedPhrase`
(background and UI) to reduce noisy reports.
> - **Dependencies**:
> - Add new yarn patch `@rive-app-canvas-patch-03752f0c3b.patch` and
update `package.json`/`yarn.lock` to chain patches for
`@rive-app/canvas@2.31.5`.
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
1f9a476. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->
@github-actions
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.

@metamaskbot metamaskbot added the team-bots Bot team (for MetaMask Bot, Runway Bot, etc.) label Nov 10, 2025
@metamaskbot
Copy link
Collaborator

Builds ready [fb7ed7c]
UI Startup Metrics (1206 ± 93 ms)
PlatformBuildTypePageMetricMean (ms)Min (ms)Max (ms)Std Dev (ms)P 75 (ms)P 95 (ms)
ChromeBrowserifyStandard HomeuiStartup1206107116049312571375
load104791913958610941202
domContentLoaded104191613878610911194
domInteractive211474121854
firstPaint62995124541410451166
backgroundConnect2292162547232240
firstReactRender24174242632
getState1973872429
initialActions001001
loadScripts819694116784865968
setupStore1063041116
numNetworkReqs1367619671
BrowserifyPower User HomeuiStartup19821767245123022932451
load1050906135816213051358
domContentLoaded1040899132315612961323
domInteractive301760165160
firstPaint857105134842413221348
backgroundConnect24222327816255278
firstReactRender29253943039
getState17015223019185230
initialActions001011
loadScripts812682109615310471096
setupStore12102541225
numNetworkReqs1167324460156244
WebpackStandard HomeuiStartup785652117384800971
load55951690569551728
domContentLoaded55251087866544717
domInteractive16116491436
firstPaint22353882212176724
backgroundConnect261284143262
firstReactRender28175283436
getState1052841216
initialActions001001
loadScripts54950787165542709
setupStore1163141219
numNetworkReqs1467620873
WebpackPower User HomeuiStartup12951156176218514451762
load67757710041538351004
domContentLoaded657566974136789974
domInteractive261389234689
firstPaint27172874220360874
backgroundConnect581122368102223
firstReactRender27242912829
getState1429416723154167
initialActions001001
loadScripts652564964132778964
setupStore1162671126
numNetworkReqs1097121444162214
FirefoxBrowserifyStandard HomeuiStartup14291274179011614981679
load1214109214628512751368
domContentLoaded1214109214628512751368
domInteractive1023531448106211
firstPaint------
backgroundConnect4125108144863
firstReactRender25215352634
getState847710622
initialActions001001
loadScripts1189107114358312551335
setupStore13680101233
numNetworkReqs1266314752
BrowserifyPower User HomeuiStartup24202094318028124973180
load13521146168418315991684
domContentLoaded13521146168418315981684
domInteractive19875569159346569
firstPaint------
backgroundConnect12838403112196403
firstReactRender482995205395
getState1118217623120176
initialActions101011
loadScripts13091122164518115751645
setupStore2361002721100
numNetworkReqs1406421357196213
WebpackStandard HomeuiStartup16041411227615316141944
load13661206166210413941617
domContentLoaded13661206166210413931617
domInteractive973136946110171
firstPaint------
backgroundConnect51241462754118
firstReactRender29228193040
getState9418919716
initialActions002001
loadScripts1335118416299613601584
setupStore187239341271
numNetworkReqs1366917764
WebpackPower User HomeuiStartup26992313367641031483676
load15791331201419216792014
domContentLoaded15781331201419216792014
domInteractive20179636184292636
firstPaint------
backgroundConnect1033632886109328
firstReactRender53401021657102
getState1269419934154199
initialActions107217
loadScripts15401311198219416221982
setupStore3462084948208
numNetworkReqs1346532891232328
📊 Page Load Benchmark Results

Current Commit: fb7ed7c | Date: 11/10/2025

📄 Localhost MetaMask Test Dapp

Samples: 100

Summary

  • pageLoadTime-> current mean value: 1.05s (±75ms) 🟡 | historical mean value: 1.04s ⬆️ (historical data)
  • domContentLoaded-> current mean value: 738ms (±90ms) 🟢 | historical mean value: 730ms ⬆️ (historical data)
  • firstContentfulPaint-> current mean value: 81ms (±50ms) 🟢 | historical mean value: 78ms ⬆️ (historical data)

📈 Detailed Results

Metric Mean Std Dev Min Max P95 P99
pageLoadTime 1.05s 75ms 1.01s 1.42s 1.26s 1.42s
domContentLoaded 738ms 90ms 703ms 1.37s 937ms 1.37s
firstPaint 81ms 50ms 60ms 572ms 84ms 572ms
firstContentfulPaint 81ms 50ms 60ms 572ms 84ms 572ms
largestContentfulPaint 0ms 0ms 0ms 0ms 0ms 0ms

@gauthierpetetin gauthierpetetin merged commit 27b8184 into release/13.9.0 Nov 10, 2025
172 of 173 checks passed
@gauthierpetetin gauthierpetetin deleted the runway-cherry-pick-13.9.0-1762775010 branch November 10, 2025 12:22
@github-actions github-actions bot locked and limited conversation to collaborators Nov 10, 2025
@metamaskbot metamaskbot added the release-13.9.0 Issue or pull request that will be included in release 13.9.0 label Nov 10, 2025
@metamaskbot
Copy link
Collaborator

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

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

release-13.9.0 Issue or pull request that will be included in release 13.9.0 team-bots Bot team (for MetaMask Bot, Runway Bot, etc.)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants