[Live Share: Guest initiated debugging] You don't have an extension for debugging .....

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

Version: 1.60.0 (user setup) Commit: e7d7e9a9348e6a8cc8c03f877d39cb72e5dfb1ff Date: 2021-09-01T10:41:52.311Z Electron: 13.1.8 Chrome: 91.0.4472.164 Node.js: 14.16.0 V8: 9.1.269.39-electron.0 OS: Windows_NT x64 10.0.18363

Steps to Reproduce:

1. Live Share host starts a collaboration session
2. Live Share guest joins session
3. Live Share guest attempts to initiate debugging

Hi @isidorn: there are a bunch of similar issues that are already closed. I’ve seen your responses that adding the debug adapter’s supported debugger “languages” to the package.json resolves the issue.

The live share guest’s debug adapter should support all languages that the host can debug though. So we would need to add every possible language so that the debug request could be forwarded to the host. If the guest is in a launch.json file they see this though:

Is there a wildcard option for all languages or a way to disable this new restriction for the Live Share guest?

[roblourens]

I’m curious how this works in other cases, as a guest do I get intellisense via LiveShare for Python files even if I don’t have the Python extension installed?

What if the host doesn’t have the debugger installed either?

if users want to debug a file for which they do not have a installed debugger (and no launch.json exists), they will no longer get the Marketplace dialog but they will end up in the LiveShare debugger instead.

And this is while not in a liveshare session? I would want to avoid things that impact the experience when the liveshare extension is installed but you are not in a liveshare session.

[roblourens]

Ping, is there anything still to be done here?