-
Notifications
You must be signed in to change notification settings - Fork 144
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debugging: ConnectionRefusedError with debugpy #84
Comments
We'll need debugpy logs to diagnose this properly - can you please add |
Also, can you try this with other Python versions (e.g. the global system one - |
I am also facing the same issue. I am also in Ubuntu 16.04 LTS. I tried to downgrade the python extension to previous versions, but then the debugger will not start(no error shown on this case just. Terminal will show the initial debug command and it will not get executed). The issue is there in python2.7 and python3.6 versions. Debuggy logs for python2.7:debugger.vscode_16c4c91a-991a-48dc-8838-ba4fb58349ae.log Debuggy logs for python3.6:debugger.vscode_5e68b1d1-d3f3-4248-a874-029aa309ad5d.log I suspect this an OS related issue because on my laptop which is using Ubuntu 18.04 LTS doesn't have this issue. This my launch.json.
VSCode Version:Version: 1.43.1 Python Extension VersionId: ms-python.python |
@tysonpaul89 I think your issue might be this one #87 Can you check the locale settings from the comments there and confirm? |
Nope, judging by the logs, it's this one. microsoft/vscode-python#10741 is almost certainly a dupe, although that one is on Windows. |
microsoft/vscode-python#10793 is another manifestation. |
The root cause for this is that we are using Until we ship the fix, the workaround is to set
However, it will not persist between reboots. To make it persistent, edit the same value in /etc/sysctl.conf. |
Always use backlog of at least 1 for listener sockets. Improve launcher-related error messages in adapter.
microsoft/vscode-python#10741 was marked as duplicate of this issue, but this issue was resolved as a Linux issue, while I'm experimenting it on Windows. Should I open a new one? |
Same here, issue is not resolved for Windows as only fix given by @int19h was for linux.. |
The error message in question is very generic - it can occur on many different code paths for many different reasons. It's preferable to file separate issues for these, and close the dupes later if investigation shows that the root cause is really the same. |
Environment data
Error
Work-around
Reverting back to previous version removes errors. The previous version uses "new_ptvsd" instead of "debugpy".
The text was updated successfully, but these errors were encountered: