Python debugger stopped working for no apparent reason

[itzsimpl]

Environment data

• VS Code version: 1.57.0-insider
• Extension version (available under the Extensions sidebar): 2021.5.842923320
• OS and version: MacOS BigSur 11.3.1 and Ubuntu 20.04
• Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
• Relevant/affected Python-related VS Code extensions and their versions: Remote-SSH 0.64.4
• Value of the python.languageServer setting: Pylance

Expected behaviour

Starting a debug session

Actual behaviour

Steps to reproduce:

When starting the session, the integrated Terminal crashes with the message "/bin/zsh: can't open input file:", see
https://user-images.githubusercontent.com/4784070/118339339-da39dd80-b518-11eb-9b2d-9c022ed3d67e.mov

On a Remote-SSH session to a Ubuntu 20.04 server, the terminal crashes with "/bin/bash: : No such file or directory"

The terminal otherwise works fine, I just cannot start a debug session. I have killed the remote server and reinstalled VSCode, nothing helps.

[itzsimpl]

Once again I have uninstalled VSCode, but this time I also deleted the following:

~/.vscode-insiders
~/Library/Preferences/com.microsoft.VSCodeInsiders.plist
~/Library/Caches/com.microsoft.VSCodeInsiders*
~/Library/Application\ Support/Code\ -\ Insiders
~/Library/Saved\ Application\ State/com.microsoft.VSCodeInsiders.savedState

and after that did a fresh install. The same error occurs.

Is there any way to debug the debugger extension (at least get a more detailed log) to see what is happening?

[csghone]

Same here - Remote SSH to Linux(Ubuntu) from Windows.

Version: 1.57.0-insider (user setup)
Commit: 40d5e6796fbc32d67dd0009e5b0027003803fd7e
Date: 2021-05-14T20:13:58.234Z (1 day ago)
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.18363

Workaround: Use "console": "internalConsole" in your debug configuration.

[itzsimpl]

Confirmed; with a specific debug configuration and "console" set to "internalConsole" instead of the default "integratedTerminal" the debugger starts up successfully. Both on MacOS BigSur, as well as Remote SSH to Ubuntu 20.04. It seems the recent changes in integratedTerminal could be the source of the problem.

[karrtikr]

Thanks for the bug report! We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.

If you think your issue is more of a question or configuration problem rather than a bug, please ask on Stack Overflow with the visual-studio-code and python labels for help.

Thanks for your understanding and patience!

[itzsimpl]

@karrtikr do check also microsoft/vscode#123949, as there was a number of other users that came forward demonstrating the same problem, but that issue was closed as it is a duplicate of this one.

[markkvdb]

I got the same error since yesterday. Everything worked fine until then. So I suspect it's not a configuration problem.

Version: 1.57.0-insider
Commit: 45aafeb326d0d3d56cbc9e2932f87e368dbf652d
Date: 2021-05-18T05:12:40.613Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Darwin arm64 20.4.0

[karrtikr]

@itzsimpl This seems like an issue on the VSCode side on the things, related to microsoft/vscode#124116 microsoft/vscode#124007 microsoft/vscode#123949. I'm transferring this issue to the debugger team to keep track of it in the extension.

[fabioz]

Well, I'm closing this on debugpy since there doesn't seem to be anything to be done here (as the issue is on VSCode itself).

The report from microsoft/vscode#124116 mentions that the current insiders build already has a fix (so, the next VSCode release should have that fixed...).

The workaround until then is using: "console": "internalConsole" in your debug configuration.