MetaMask / MetaMask/metamask-extension
[Sentry] Error: Non-200 status code: '400'
- Dominant language
- TypeScript
- Stars
- 13.2k
- Forks
- 5.6k
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 451
Description
Sentry Issue: [METAMASK-XK7W](https://metamask.sentry.io/issues/6616164529/?referrer=github_integration)
```
Error: Non-200 status code: '400'
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.rpcErrorsinternal (node_modules/@metamask/rpc-errors/dist/errors.cjs:42:1)
at _RpcService_processRequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:318:1)
at exports.RpcServicerequest (node_modules/@metamask/network-controller/dist/rpc-service/rpc-service.cjs:240:1)
...
(2 additional frame(s) were not displayed)
```
Contributor guide
Research direction
Start with the linked Sentry report and the stack trace, then inspect the @metamask/network-controller RPC service request path shown in the error. Determine which request produces the 400 response and establish a reproducible failure; the issue provides no acceptance criteria or named test for verifying a fix.
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
- 25/100