microsoft / microsoft/vscode-cpptools
Add telemetry when language service is unresponsive
Open
Nobody has claimed this yet.
enhancement
Language Service
telemetry
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
There are various ways we could detect an unresponsive cpptools process.
Example of an issue is https://github.com/microsoft/vscode-cpptools/issues/6149 .
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
The issue names no files, tests, or entry points. Start by reviewing the linked cpptools issue 6149 and the repository's language-service and telemetry areas to determine how unresponsiveness could be detected. Done should include an agreed detection approach and telemetry for the unresponsive cpptools process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- observability
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100