Error "You don't have an extension of ..." with debugger extension

[Sen-real]

Hi experts,

With VS Code 1.56, we get a new problem with our debugger extension:
Autodesk-AutoCAD/AutoLispExt#143

It seems common, as I found a similar problem here:
https://stackoverflow.com/questions/67430297/vscode-you-dont-have-an-extension-for-debugging-html-error

With our debugger extension activated, when starting to debug wth F5, an error dialog of "You don't have an extension of ..." shows up. It suggests to find our extension in the Marketplace.

But as suggested in the page above, the error is gone after we manually added a configuration file for our debugger extension.

Is this a new requirement that a user of a debugger extension must first author a configuration file before starting to debug? or is there some changes in VS Code debugger API that we should apply?

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• All my debuggers are gone (#123341)
• After starting the debugger, debugger popup stops suddenly. (#120051)

[egamma]

Duplicate of #123106 will be fixed in 1.56.2

[nigma456]

Duplicate of #123106 will be fixed in 1.56.2

This issue is not fixed in latest 1.56.2 and even 1.57.

[Sen-real]

@egamma @isidorn
It's NOT fixed with 1.56.2. Here's a video made with 1.56.2:
https://user-images.githubusercontent.com/57521938/118391492-2430d980-b667-11eb-90d5-5ea7e599750e.mov
My VSCODE:

[isidorn]

@Sen-real you are showing a different issue, that is for the .lsp file
In order to fix that your debugger extensino has to say it is interested in .lsp language files. You can do that by listing this in your package.json. Here's an example how mock debug does it https://github.com/microsoft/vscode-mock-debug/blob/main/package.json#L135

[Sen-real]

@Sen-real you are showing a different issue, that is for the .lsp file
In order to fix that your debugger extensino has to say it is interested in .lsp language files. You can do that by listing this in your package.json. Here's an example how mock debug does it https://github.com/microsoft/vscode-mock-debug/blob/main/package.json#L135

@isidorn:
Thanks for looking at this issue. We have two languages listed in package.json:
https://github.com/Autodesk-AutoCAD/AutoLispExt/blob/main/package.json#L373, and
https://github.com/Autodesk-AutoCAD/AutoLispExt/blob/main/package.json#L385
Should they be updated somehow?

[isidorn]

@Sen-real I think you overdid it there a bit. The languages array inside the debuggers is an array of strings, not objects. So just try
"languages": ["autolist", "autolistdcl"]

And the full language details should be contributed I think in another package.json place, not inside debuggers

[Sen-real]

Thanks! let me try.

[Sen-real]

@isidorn
I just tried the change you suggested. It works well with a ".lsp" file opened in VS Code.
But, if I open NO folder or file, when I click "Run -> Start Debugging", there's still one difference:

Is the new result with 1.56.2 by design?

[isidorn]

Great thanks.
That one should be fixed in insiders and should be available in the next stable in 1 month

[Sen-real]

Great thanks.
That one should be fixed in insiders and should be available in the next stable in 1 month

Cool, thanks!

[Sen-real]

@isidorn
I can't reopen this issue. Should I report a new one?

[isidorn]

Nope, already fixed.