microsoft / microsoft/vscode-cpptools
Disable logging for first chance exceptions but not unhandled exceptions
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 6.2k
- Forks
- 1.7k
- Avg merge
- 14h 46m
- Merged PRs (30d)
- 61
Description
The codebase I'm currently working has a dependency that uses exceptions for flow control. The (handled) first chance exceptions get logged and it causes so much spam it makes the console useless. I have to disable logging.exceptions in my launch configuration, but that has the side effect of disabling all exceptions. Now when a real exception occurs I can't see it in the console.
I'd like to be able to disable first chance exceptions without disabling unhandled exceptions.
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 by examining how the launch configuration's logging.exceptions setting is handled and how exception events reach the console. The change is complete when first-chance exceptions can be suppressed without hiding unhandled exceptions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100