MetaMask / MetaMask/metamask-extension
[Sentry] Error: RPC endpoint not found or unavailable.
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-XPHP](https://metamask.sentry.io/issues/6819274629/?referrer=github_integration)
```
Error: RPC endpoint not found or unavailable.
at new JsonRpcError (node_modules/@metamask/rpc-errors/dist/classes.cjs:33:1)
at getJsonRpcError (node_modules/@metamask/rpc-errors/dist/errors.cjs:176:1)
at exports.rpcErrorsresourceUnavailable (node_modules/@metamask/rpc-errors/dist/errors.cjs:81:1)
at _RpcService_processRequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:356:1)
at exports.RpcServicerequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:277:1)
...
(2 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start with the linked Sentry report and the @metamask/network-controller RPC service entry points shown in the stack trace. Establish which request and endpoint trigger the resource-unavailable error, then add a regression test and verify that the affected RPC request behaves correctly without reproducing the reported failure.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100