Debug flow

[bamurtaugh]

Testing microsoft/vscode-python#18092

• Open https://github.com/microsoft/vscode-remote-try-python with GitHub Repositories in VS Code desktop
• Go to Run and Debug
• If I was new to this flow, I'd want to and wonder how to run my app
  • I think a user would need to continue locally?
  • Could we indicate this in the message and perhaps guide users there via messaging/a button (i.e. to "Continue Working on" locally), rather than saying it's not supported in the current environment and prompting to open the launch.json?

@joyceerhl @karrtikr @kimadeline Although the test plan item came from the vscode-python repo, I thought this flow may be part of GitHub Repositories and/or debugging overall, so filing here. Please let me know if I should file elsewhere or it's already being tracked/considered. Thank you!

[joyceerhl]

Still repros:

Should the Python extension not contribute launch configurations when in a virtual workspace on desktop?

[karrtikr]

This is where we disable the debug configuration view for virtual workspaces if that's relevant: https://github.com/microsoft/vscode-python/blob/983a8dfd4c8eb524614490b2e63bc894a859cb72/package.json#L1509

[brettcannon]

Do we have the appropriate hooks already to intercept this to suggest people run locally? As Kartik pointed out we can probably disable debugging for virtual workspaces (although it looks like we already do something which is probably what's making the prompt show up to begin with).