I'm running the visual studio code tutorial with Python and am unable to connect to the debugger. Google / SO are coming up empty when I search. Usually I use Anaconda with Jupyter, so I'm connecting Visual Studio Code to the python in my activated 3.6 virtual environment. I tried pip installing ptvsd in my virtual environment, but that did not make a difference in what I am seeing.
I would welcome any suggestions. Screenshots included below. launch.json in the bottom screenshot
Open the launch.json file and add the following configuration:
{
"name": "Python: Debug Console",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "internalConsole"
}
When you specify noneinternalConsole for the console, it will run the debugger in the debugger console instead of running in the internal or external terminal.
I had the same issue, so I added the following line to the
settings.json file:
{
// to fix 'Timeout waiting for debugger connections'
"python.terminal.activateEnvironment": false
}
I had this same problem today. I think it might be a connection problem when the debugger tries to connect to an integrated PowerShell terminal inside Visual Studio. If I change to using an external terminal to run the program then it works okay, and the debugger connects to the external terminal and I can debug perfectly fine. This is my entry for the external terminal launch in launch.json
{
"name": "Python: Terminal (external)",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "externalTerminal"
},
I had the same issue.
Fixed it by using "integratedTerminal".
PS: My system is Windows 7.
{
"name": "Debug",
"type": "python",
"request": "launch",
"program": "${workspaceFolder}/main.Py",
"console": "integratedTerminal"
}
Change your integrated terminal shell to cmd.exe. This will allow the default launch.json to debug with the Current File (Integrated Terminal) option.
How to switch from powershell.exe to cmd.exe: Visual Studio Code, how to switch from powershell.exe to cmd.exe
More information about the integrated terminal: https://code.visualstudio.com/docs/editor/integrated-terminal
This change has fixed other bugs in my Visual Studio Code + Python integration, such as the double call to Run Python File in Terminal that was frequently required. It was a nice suggestion coming from an internal dialog in version 1.28.2.
I had the same issue today. The reason was that the debug settings were changed to "Current File (Integrated Terminal). Switching back to "Debug Console" fixed the problem for me.
I think this is going to work fine, I tried it:
"configurations": [
{
"name": "Python: Debug Console",
"type": "python",
"request": "launch",
"program": "${file}",
"console": "integratedTerminal"
}
]
As I see by others' answers, the problem itself may differ from case to case. In my case, I had the gdb package missing. After reinstalling it with sudo apt-get update; sudo apt-get install gdb, I was able to use the debugger.
But if it doesn't help you, here is a nice way to find a reason in your case.
launch.json file and add "logToFile": true flag./root/.vscode-server/extensions/ms-python.python-2022.8.0 (it may differ based on your version of the Python VS code extension). The files you're looking for has the .log extension obviously
I got here using WSL.
I tried to restart a debug session and vs code just dropped back to the prompt. When I ran debug again it timed out as per the OP's error.
Solution was to kill the previous debug session in WSL bash (or vs code bash for that matter), one liner:
sudo kill -9 `ps ax | grep python | grep 5678 | cut -d' ' -f1`
Debug should work again.
Add cmd to your environment variables
That helped me to solve the problem.
You need to add the following path to your system variables path.
%SystemRoot%\system32
Good luck, I hope it solved your problem.
Changing your "integratedTerminal" shell to cmd.exe will fix it, because it's using "PowerShell".
I tried all the solutions that have been mentioned here. Nothing worked. Figured out the default timeout in debugpy that VSCode uses is 15 seconds. So if your app doesn't launch within 15 seconds, then VSCode throws this exception.
Solution that works: Create a new environment variable in your user account (not in launch.json) DEBUGPY_PROCESS_SPAWN_TIMEOUT and set it to 90
On Windows:
The highest-voted answer worked for me, but:
That is, you can continue to use launch.json "console": "integratedTerminal", but change your default terminal profile to the Command Prompt:
(My suggestion is better if you prefer to see Command Prompt output in the opened terminal. But my suggestion is worse if you don't care about Command Prompt output, and/or you don't want to change your default terminal for whatever reason)
EDIT 1: More context
I deleted details (see history of my edits), but in case they help other people find this question & answer, note if you use "Git Bash" as your integrated terminal and you try to debug you may see this error in the terminal after the "Timed out" dialog appears:
More details:
File "<frozen runpy>", line 198, in _run_module_as_main
File "<frozen runpy>", line 88, in _run_code
File "c:\Users\username\.vscode\extensions\ms-python.python-2023.8.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher\__main__.py", line 91, in <module>
main()
File "c:\Users\username\.vscode\extensions\ms-python.python-2023.8.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher\__main__.py", line 47, in main
launcher.connect(host, port)
File "c:\Users\username\.vscode\extensions\ms-python.python-2023.8.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher/../..\debugpy\launcher\__init__.py", line 34, in connect
raise e
File "c:\Users\username\.vscode\extensions\ms-python.python-2023.8.0\pythonFiles\lib\python\debugpy\adapter/../..\debugpy\launcher/../..\debugpy\launcher\__init__.py", line 30, in connect
sock.connect((host, port))
ConnectionRefusedError: [WinError 10061] No connection could be made because the target machine actively refused it
EDIT 2: Another answer works
This other answer also works for me, without changing my terminal (i.e. still using Git Bash as my default terminal and using "console": "integratedTerminal" in my launch.json
I used a higher value (180) for the DEBUGPY_PROCESS_SPAWN_TIMEOUT environment variable, and I checked echo $DEBUGPY_PROCESS_SPAWN_TIMEOUT actually printed the value.
My "Git Bash" is slow to open in general (even without VS Code). Try opening your Git Bash after a fresh restart of your windows machine; if it takes longer than 15 seconds (default value for DEBUGPY_PROCESS_SPAWN_TIMEOUT), that explains the timeout! (Whereas opening my Command Prompt goes very quickly, which explains why using Command Prompt instead can work!)
have you ever changed the default terminal shell of vs code? I ran into the same question after changed the shell of vs code from "cmd" to "msys2". and configure below worked, though I dont know why. "python.terminal.activateEnvironment": false
Personnaly I had the issue when having my working directory in a remote location (local network on a NAS). Copying the directory in my machine and working from there solves the issue.
