Plugins should be attached to backtrace reports
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- C++
- Stars
- 16.2k
- Forks
- 1.9k
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 80
Description
Any loaded plugins should have their .js file attached to the backtrace report that is uploaded.
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
No file, test, or entry point is named. Start by locating the backtrace report upload path and the code that tracks loaded plugins. Done means each loaded plugin's .js file is attached to the uploaded backtrace report, with coverage for the behavior verified by the relevant test or report workflow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, javascript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100