Timed out error while using debugpy in IntegratedTerminal
@debonte is already working on this.
Since Nov 18, 2024.
Assessment
This issue has not been assessed yet.
Description
I am pretty new to VSCode so sorry in advance if I am not providing enough information.
I am using macOS Sonorama 14.5 using VSCode with:
Version: 1.95.3
Commit: f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin x64 23.5.0
While working with Python 3.13.0 from a virtual environment, if I try to run the following launch.json configuration:
{
"name": "main",
"type": "debugpy",
"request": "launch",
"program": "${workspaceFolder}/src/main.py",
"console": "integratedTerminal",
"logToFile": true,
"cwd": "${workspaceFolder}",
"env": {
"PYTHONPATH": "${cwd}"
}
}
I get the following error:
The debubpy extension logs are:
2024-11-17 03:40:49.650 [info] Resolving launch configuration with substituted variables
2024-11-17 03:40:49.656 [info] DAP Server launched with command: /Users/jorgepose/Desktop/Code/LearningPandas/.venv/bin/python /Users/jorgepose/.vscode/extensions/ms-python.debugpy-2024.10.0-darwin-x64/bundled/libs/debugpy/adapter --log-dir /Users/jorgepose/.vscode/extensions/ms-python.debugpy-2024.10.0-darwin-x64
2024-11-17 03:40:50.231 [info] Received 'debugpySockets' event from debugpy.
2024-11-17 03:40:50.237 [info] Received 'debugpySockets' event from debugpy.
2024-11-17 03:40:50.238 [info] Received 'debugpySockets' event from debugpy.
If I change the "console" to "internalConsole" I don't get such error and the code runs fine. I tried using previous versions of both vsCode and debugpy but that didn't work, and doing it while not having any other extension installed also gives the same error. From what I've seen in other issues, in Windows it's already fixed but I don't know if someone else is having this problem with Mac
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 202
- Avg merge
- 5d 1h
- Merged PRs (30d)
- 1
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/debugpy
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
All issues in microsoft/debugpy
Similar issues
-
essnmx good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
[Feature] 奇物选择添加优先级 Open
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
syfoud/Simulated_Scepter#174 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Giskard-AI/giskard-oss#2840 · 1 comment ·
-
A claim comment carrying the issue number is silently declined while the workflow reports success Openarea: repo bug perceived difficulty: 2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
yeti-platform/yeti#1380 ·