MetaMask / MetaMask/metamask-extension
[Sentry] Error: Event fragment with id transaction-added-9f549c00-9a9d-11ef-84a4-378765c7386b does not exist.
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-MPRF](https://metamask.sentry.io/issues/3055955747/?referrer=github_integration)
```
Error: Event fragment with id transaction-added-9f549c00-9a9d-11ef-84a4-378765c7386b does not exist.
at exports.defaultupdateEventFragment (app/scripts/controllers/metametrics.js:349:13)
at ReflectApply (app/scripts/lib/createMetaRPCHandler.js:23:31)
...
(12 additional frame(s) were not displayed)
```
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 in app/scripts/controllers/metametrics.js at line 349, where updateEventFragment reports the missing event fragment, and trace the call through app/scripts/lib/createMetaRPCHandler.js. Reproduce or follow the fragment lifecycle to determine why the transaction-added fragment is unavailable; done means the failure is understood and the missing-fragment error no longer occurs or is handled appropriately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- analytics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100