MetaMask / MetaMask/metamask-extension
[Sentry] Error: RPC endpoint returned HTTP client error.
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-XPHE](https://metamask.sentry.io/issues/6819093564/?referrer=github_integration)
```
Error: RPC endpoint returned HTTP client error.
at new JsonRpcError (node_modules/@metamask/rpc-errors/dist/classes.cjs:33:1)
at _RpcService_processRequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:364:1)
at exports.RpcServicerequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:277:1)
at (node_modules/@metamask/eth-json-rpc-middleware/dist/fetch.js:43:1)
at (node_modules/@metamask/json-rpc-engine/dist/createAsyncMiddleware.cjs:49:1)
```
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Sentry issue and the stack frames in @metamask/network-controller's rpc-service and @metamask/eth-json-rpc-middleware's fetch.js. Determine which RPC request produces the HTTP client error and whether it can be reproduced locally. Done means the cause is identified and the affected RPC path no longer reports the failure unexpectedly, with coverage for the case if the project provides a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100