vscode: Debugger stopped working when installing 1.74 in MacOS Ventura

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.74
OS Version: MacOS Ventura 13.0.1

Steps to Reproduce:

Open my TypeScript project
Set some breakpoints
The breakpoints are enabled
The breakpoints are not hit

Other things I’ve tested:

I’ve tested this with Insiders and VSCodium 1.74. The issue is always present.
I’ve tested this with VSCode < 1.74, and the debugger starts to work again.
I’ve tested this with VSCode 1.74 in Monterrey and it works.
I’ve tested this with another project and it works. The main difference I can see is that the one that works is not running from bundled code.

I’ll try to update this issue with some project I can share exposing this behavior.

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 7
Comments: 29 (22 by maintainers)

Commits related to this issue

fix: better handling of multiple/relative outFiles Fixes #1479 Relates to https://github.com/microsoft/vscode/issues/168635 Previously, we naively joined all incoming globs together and ran a single... — committed to microsoft/vscode-js-debug by connor4312 2 years ago

Most upvoted comments

FYI, I cannot reproduce the issue anymore with the latest v1.74.1 update.

robertohuertasm on Dec 15, 2022

From what I’m seeing, the API assumes that there is only one glob assigned to include. For the case where you want to match two globs, we have internal support for that (ie: with the search viewlet), but I don’t think there’s a clear way to do it with the API (as you probably saw before).

Instead of passing in comma-separated globs, perhaps allowing include to be GlobPattern | GlobPattern[] would help? I was originally thinking that we could keep doing comma-separated values, but I think that search does extra work with the input paths to generate the actual paths that ripgrep uses (https://github.com/microsoft/vscode/blob/ab1a31add4608f484d555e3c791f03321a4dda5f/src/vs/workbench/services/search/node/ripgrepTextSearchEngine.ts#L498)

I’m not too sure what behavior you were seeing before with the comma-separated system working?

andreamah on Dec 13, 2022