Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Make the debug_session.error telemetry event capture only debugging errors, not regular debug exit #526

Open
luabud opened this issue Nov 29, 2021 · 2 comments
Open

Make the debug_session.error telemetry event capture only debugging errors, not regular debug exit #526

luabud opened this issue Nov 29, 2021 · 2 comments
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. needs PR Ready to be worked on

Comments

@luabud
Copy link
Member

luabud commented Nov 29, 2021

No description provided.

@luabud luabud added the debt Covers everything internal: CI, testing, refactoring of the codebase, etc. label Nov 29, 2021
@github-actions github-actions bot added the triage-needed Needs assignment to the proper sub-team label Nov 29, 2021
@karthiknadig karthiknadig removed the triage-needed Needs assignment to the proper sub-team label Nov 29, 2021
@kimadeline
Copy link

On regular exit the onError handler is triggered with the following error:

message:'read error'
stack: 'Error: read error
at Socket. (/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/services/extensions/node/extensionHostProcess.js:90:2066)
at Socket.emit (events.js:327:22)
at Pipe. (net.js:673:12)
at Pipe.callbackTrampoline (internal/async_hooks.js:131:14)'

Need to figure out how to not receive this error, or if it's safe to ignore it.

@karrtikr karrtikr added the needs PR Ready to be worked on label Aug 9, 2022
@eleanorjboyd
Copy link
Member

@luabud could you elaborate on this? Wondering if this still applies since the move to the separate debug extension

@eleanorjboyd eleanorjboyd transferred this issue from microsoft/vscode-python Dec 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
debt Covers everything internal: CI, testing, refactoring of the codebase, etc. needs PR Ready to be worked on
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@karthiknadig @karrtikr @eleanorjboyd @luabud @kimadeline