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(deps): update from eth-rpc-errors to @metamask/rpc-errors #22871

Closed
wants to merge 17 commits into from

Conversation

legobeat
Copy link
Contributor

@legobeat legobeat commented Feb 8, 2024

Description

The package eth-rpc-errors has been renamed to @metamask/rpc-errors starting with version 5. Many controllers and libraries used in extension already use the releases. This updates the direct dependency from [email protected] to @metamask/[email protected].

Related issues

Blocking

Manual testing steps

Screenshots/Recordings

Before

After

Pre-merge author checklist

  • I’ve followed MetaMask Coding Standards.
  • 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 format if applicable
  • I’ve applied the right labels on the PR (see labeling guidelines). 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.

Copy link
Contributor

github-actions bot commented Feb 8, 2024

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.

@legobeat legobeat force-pushed the deps-eth-rpc-errors branch from 31e4a2a to b075fa9 Compare February 8, 2024 10:18
@legobeat legobeat added dependencies Pull requests that update a dependency file team-security labels Feb 8, 2024
@FrederikBolding
Copy link
Member

🎉

FrederikBolding
FrederikBolding previously approved these changes Feb 8, 2024
Copy link
Member

@FrederikBolding FrederikBolding left a comment

Choose a reason for hiding this comment

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

Code LGTM, but looks to be some problems in CI.

@legobeat
Copy link
Contributor Author

legobeat commented Feb 8, 2024

Code LGTM, but looks to be some problems in CI.

Addressed in c81c503 by updating tests to expect underlying error message in cause.

@legobeat legobeat marked this pull request as ready for review February 8, 2024 11:41
@legobeat legobeat requested review from a team as code owners February 8, 2024 11:41
FrederikBolding
FrederikBolding previously approved these changes Feb 8, 2024
@legobeat legobeat marked this pull request as draft February 8, 2024 12:15
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch 7 times, most recently from 5d38fdd to 4284831 Compare February 8, 2024 18:50
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch 2 times, most recently from 79e9598 to 7f3572e Compare February 22, 2024 04:34
@legobeat legobeat changed the title deps: update from eth-rpc-errors to @metamask/rpc-errors fix(deps): update from eth-rpc-errors to @metamask/rpc-errors Feb 23, 2024
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch 3 times, most recently from b82f0e9 to d09d8f7 Compare March 11, 2024 01:14
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch from d09d8f7 to 892b0cc Compare April 18, 2024 23:13
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch 5 times, most recently from 62c8115 to 95eca84 Compare May 31, 2024 01:58
@legobeat legobeat force-pushed the deps-eth-rpc-errors branch from 95eca84 to 61a4717 Compare May 31, 2024 04:01
@Mrtenz Mrtenz removed their request for review July 4, 2024 09:12
Copy link
Contributor

github-actions bot commented Sep 2, 2024

This PR has been automatically marked as stale because it has not had recent activity in the last 60 days. It will be closed in 14 days. Thank you for your contributions.

@github-actions github-actions bot added the stale issues and PRs marked as stale label Sep 2, 2024
Copy link
Contributor

This PR was closed because there has been no follow up activity in the last 14 days. Thank you for your contributions.

@github-actions github-actions bot closed this Sep 16, 2024
Gudahtt pushed a commit that referenced this pull request Oct 16, 2024
…edition) (#24496)

## **Description**

- Upgrade from obsolete `eth-rpc-errors` to `@metamask/rpc-errors`
  - This introduce handling of error causes 


See [here](MetaMask/rpc-errors#140) for some
context.

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

## **Related issues**

- #22871

#### Blocked by
- [x] MetaMask/rpc-errors#158
- [x] MetaMask/rpc-errors#144
  - [x] MetaMask/rpc-errors#140

#### Blocking
- #22875

## **Manual testing steps**

## **Screenshots/Recordings**

### **Before**

### **After**

## **Pre-merge author checklist**

- [x] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.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/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.
Gudahtt pushed a commit that referenced this pull request Oct 21, 2024
…edition) (#24496)

- Upgrade from obsolete `eth-rpc-errors` to `@metamask/rpc-errors`
  - This introduce handling of error causes

See [here](MetaMask/rpc-errors#140) for some
context.

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

- #22871

- [x] MetaMask/rpc-errors#158
- [x] MetaMask/rpc-errors#144
  - [x] MetaMask/rpc-errors#140

- #22875

- [x] I’ve followed [MetaMask Coding
Standards](https://github.com/MetaMask/metamask-extension/blob/develop/.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/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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file stale issues and PRs marked as stale team-security
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

4 participants