CTRL-C is immediately issued upon run, execution gets cancelled by activation command

[raydrak64]

Happens on multiple Ubuntu 24.04 workstations but not on any Windows 11 machines.
All machines are configured with the suggested fixes/settings per your emails for the Python Env extension, that seems to be doing well.

However...

Either from the hotkey or from the menus, when you run a Python file a CTRL-C is immediately issued. It is consistently intermittent, meaning, it's not 100% of the time but from observation it is 75-80% of the time. So, 8 out of 10 times you have to run the script again...and again... until it runs as expected. Sometimes you get lucky, and the CTRL-C is thrown to soon to interfere, like right before the venv is activated.

Thanks folks and cheers!

[eleanorjboyd]

Hi! Thanks for the issue report and sorry this is happening! How are you running your python file? ie what command, entry point, and environment manager? This might give us a clue. Also is it CTRL-C specifically or does the terminal just reload? We were seeing that occur with some other users and wondering if they are connected

[raydrak64]

Hello. Thank you for responding. I am awkward in giving information on issues so thank you.
I will answer in bullet points:

• How the file is being ran: Pull down menu: Run -> Run Without Debugging -or- hotkey (CTRL+F5)
• Environment Manager: Microsoft Python Environments or if you mean Python distro, just good ol' plain CPython and pip
• The terminal does not reload
• It is CTRL-C specifically... you see the ^C in the terminal and immediately shuts the party down like it's the cops

This has been happening for a while. Even before the venv fiasco. I just thought I'd say something now since in a communique it was said y'all be focusing on the Python Environments extension. This did not happen with the old extension, so I kept that installed until it stopped working altogether. Then I just never kept MS Python Environments installed because it would do this as soon as it was installed. But I have it installed now of course, and this is the only hiccup.

This is happening on all the Ubuntu 24.04 installs, so I am surprised it wasn't brought up by someone else.

Cheers!

[github-actions]

Hey @eleanorjboyd, this issue might need further attention.

@raydrak64, you can help us out by closing this issue if the problem no longer exists, or adding more information.

[raydrak64]

It still exists. Every 7 or 8 out of 10 attempts to run a python script through VSC results in CTRL-C being thrown. It doesn't matter the project or where it's being run. You have to run it multiple times before CTRL-C is not being thrown automatically.

I don't bother anymore. Just run a terminal at the location and run the script manually. Debug or run the script manually in a separate terminal window.

^C..^C...^C....^C......^C....^C.....ok....is my life...

[karthiknadig]

@anthonykim1 can you help with this? We don’t send ctrl-c to the terminal. This is coming from shell integration feature of VS Code.

[anthonykim1]

@raydrak64 Thanks for filing the issue. Can you record a short video/gif for this?
Also wondering how frequent you are running the file consecutively.

And yes, this is likely coming from executeCommand of shell integration.
It would be clear yes if you test this by turning off terminal.integrated.shellIntegration.enabled and try running via run button and see if ^C does not persist.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!

[raydrak64]

@raydrak64 Thanks for filing the issue. Can you record a short video/gif for this? Also wondering how frequent you are running the file consecutively.

And yes, this is likely coming from executeCommand of shell integration. It would be clear yes if you test this by turning off terminal.integrated.shellIntegration.enabled and try running via run button and see if ^C does not persist.

@anthonykim1 I tried turning off the setting suggested and the ^C issue persisted.

Unfortunately, I am unable to provide video of the issue. But I can give a textual account:
Script is to just output on the screen: "I am really wanting to run this script in VS Code."
Run = Shift+F5 or from the pull down menus: Run without Debugging
Stop = Hitting the Red Square on the running script/application bar that appears when running something within VS Code

[] Run
[] Output: I am really wan^C
Keyboard Interrupt Error...
[] Stop.........Stop...........Stop..........Stop............ok

[] Run
[] Output: I^C
Keyboard Interrupt Error....
[] Stop.........stop.........ok

[] Run
[] Output: ^C
Could not initialize.......
[] Stop........ok

[] Run
[] Output: I am really wanting to run this scri^C
Keyboard Interrupt Error...
[] Stop......stop........stop.........................stop........................stop................stop............ok

[] Run
[] Output: I am really wanting to run this script in VS Code.
[] Ok: (.venv) -$ x

That's it exactly....no more or less. I just work around it by keeping a regular terminal open on another screen and run all debugs and tests outside VS Code. I would love to be able to mindlessly hit F5 and a detached VS Code terminal window opens and runs the script doing all the fancy stuff.

Cheers!
-Ray

[anthonykim1]

Did you make sure @raydrak64 to turn off terminal.integrated.shellIntegration.enabled for both user and workspace setting?
Otherwise ^c showing up doesnt make sense.