microsoft / microsoft/CLRInstrumentationEngine
Define story for triaging bugs/errors when multiple profilers conflict.
Open
Nobody has claimed this yet.
task
- Dominant language
- C++
- Stars
- 102
- Forks
- 52
- Avg merge
- 13h 11m
- Merged PRs (30d)
- 6
Description
This task is necessary for root-causing and routing errors to affected profilers in the case where multiple profilers conflict with each other.
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 issue description and define the story for triaging errors when multiple profilers conflict. Document how root-cause information should identify affected profilers and how errors should be routed. Done means the story has an agreed scope and clear acceptance criteria for these conflict cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100