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.

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

noDebug: true debugs #101413

Closed
jrieken opened this issue Jun 30, 2020 · 4 comments
Closed

noDebug: true debugs #101413

jrieken opened this issue Jun 30, 2020 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s)

Comments

@jrieken
Copy link
Member

jrieken commented Jun 30, 2020

Testing #100963

  • have an extension sample, set a breakpoint on first line in activate-function
  • debug from the viewlet, breakpoint hit, stop debugging
  • have the snippet below
  • debug via the command
  • 🐛 breakpoint hit

	vscode.commands.registerCommand('extension.helloWorld', async (args) => {
		try {
			const session = await vscode.debug.startDebugging(vscode.workspace.workspaceFolders![0], 'Run Extension', { noDebug: true })
			console.log('DEBUG', session)
		} catch (err) {
			console.error(err);
		}
	});
@isidorn
Copy link
Contributor

isidorn commented Jun 30, 2020

This is probably becauase js-debug currently does not support noDebug. So first assigning to @connor4312
@jrieken as a workaround you can set "debug.extensionHost.useV3": false, and that should make you use the old node debugger

@connor4312
Copy link
Member

Duplicates microsoft/vscode-js-debug#523. I'm probably going to fix this in my run of the test plan.

@connor4312 connor4312 added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 30, 2020
@connor4312
Copy link
Member

Fixed in the next nightly

@github-actions github-actions bot locked and limited conversation to collaborators Aug 14, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s)
Projects
None yet
Development

No branches or pull requests

4 participants
@jrieken @isidorn @connor4312 and others