Adapter descriptor ERROR "No delegateCommandHandler for vscode.java.validateLaunchConfig" about vscode-java-debug HOT 2 CLOSED

The pre-release version 0.56.2024022605 should have fixed this issue.

from vscode-java-debug.

Ok, VSCode Bisect is a blunt tool. It doesn't allow you to reserve some extensions as important, so if a syntax highlighter conflicts with a debugger, it's just as likely to blame the debugger and disable it so you can keep using the easily replaceable syntax highlighter.

I like the idea of Bisect, but it's too blunt.

I wrote this simple PowerShell script to loop through my extensions, and I believe I have identified that something is conflicting with this debugger.

code-insiders --list-extensions --profile $profile | Set-Variable extensions

Get-Content "$extensionsFile" | ForEach-Object {
    if($_ -match "^#") {
        if($extensions -contains $_.Replace("# ", "")) {
            Write-Host "UNinstalling $_"
            code-insiders --profile $profile --uninstall-extension $_.Replace("# ", "") 2>$null
        }
    } else {
        if($extensions -notcontains $_) {
            Write-Host "Installing $_"
            code-insiders --profile $profile --install-extension $_ 2>$null
        }
    }
}

I will have more info shortly and I think I will be able to close this ticket soon.

from vscode-java-debug.