-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
ConnectionRefusedError: [WinError 10061] when press F5
to start debugging
#10741
Comments
You mention that with Also, can you please try adding |
@int19h Here is my Hope these may help you. PS: Is it possible that these problems are caused because I'm using git bash as my terminal? (But I didn't face these problems in previous versions) Thanks. |
I can't think of any reason why Bash would make a difference... but other repros that we're seeing are all on Linux, so perhaps it is related. Could you switch to cmd.exe temporarily, and try it with and without activation, to see if that matters? |
@int19h |
@int19h |
Thank you very much - this is incredibly helpful! |
I actually have that same issue when connecting to a remote device (using SSH remote), both from my Mac and from my Windows machine.
This didn't happen a few days ago. I also don't have a conda environment in this case, I'm using the OS python installation. This happens to be an NVIDIA Jetson device, so unable to easily install conda there. |
Update: |
microsoft/debugpy#84 is the primary issue tracking this bug now, so I'll close this one as a dupe. |
Environment data
Expected behaviour
The debugger should start and enter a debug session
Actual behaviour
Fail to start the debugger when I press
F5
.It first print the following sentence in the terminal:
Then pop up the warning:
Then print the following sentences:
The chinese means
Unable to connect because the target computer actively refuse
Steps to reproduce:
print('helloworld')
F5
Logs
Output for
Python
in theOutput
panel (View
→Output
, change the drop-down the upper-right of theOutput
panel toPython
)Output from
Console
under theDeveloper Tools
panel (toggle Developer Tools on underHelp
; turn on source maps to make any tracebacks be useful by runningEnable source map support for extension debugging
)Here I only paste what is printed after I press
F5
Other info I think may be helpful
My launch.json:
My settings.json
And, when I add
"python.terminal.activateEnvironment": false
to the settings.json, the warning no longer appear. But I still prefer to activate environment when starting debugger. Also it seems to ocasionally suceed after several minutes but I don't think it's a good way to face the problem.The text was updated successfully, but these errors were encountered: