execution timeout for some reason?

[Ryswyn]

import time

init = (time.time())
while True:
    init2 = (time.time()) - init
    print(f"\r{init2}", end="", flush=True)
#prints time diff

a small counter i made while studying.

when i ran it, i kept getting keyboard interrupts at around 5 sec.

my solution was to add "terminal.integrated.shellIntegration.enabled": false to the user setting.json
or to disable Python Environments

the issue only exists if Python Environments and shell integration is enabled

another interesting fact is that if i added ""code-runner.executionTimeout": -1" to user settings.json and restarted vscode, then the issue was also resolved but after like 30min when i ran the code again, the issue came back. which is interesting because i dont have code runner installed.

1. Enable Python Environments + shell integration
2. Create a Python file with an infinite loop that does something(while True: pass works fine)
3. Run it in the VS Code integrated terminal
4. a KeyboardInterrupt exception is raised after ~5 sec

expectation: no keyboard interrupt after any amount of time that was not intended
reality: keyboard interrupt exception is raised after ~5 sec

versions:
Python Environments: 1.22.0
Vscode: 1.111.0
OS: linux mint 22.3
btw i tested this with different extension configurations and even if only Python and Python Environments enabled it still happens.

p.s. first time submitting a bug on github so ill be checking every now and then to see if any other info is requested

edit: also i didnt realise this at first but if "python.experiments.enabled": false in settings.json, the issue exists, but goes away if true
edit: experimental sometimes fixes the issue but not always idk

[eleanorjboyd]

Hi! Could you clarify which settings you are setting and what you then see? Specifically for python.useEnvsExtension and terminal.integrated.shellIntegration.enabled. I am a bit confused with the experimentation on and off since experiments impact settings as well

[Ryswyn]

when you set that to false, /home/user/.config/Code/User/settings.json gets another item added to it: "terminal.integrated.shellIntegration.enabled": false

when i turned on experiments again, my issue appearing went from consistent to inconsistent(havent read the source code for experiments so couldn't even guess why), meaning it was honestly a guess for whether it would appear

these are the only extensions i had enabled(minus python environments when i implemented the fix*)

screenshot after it got interrupted

also, just checked my settings, and python.useEnvsExtension was disabled(even though as in the picture above i enabled the extension elsewhere). after i enabled python.useEnvsExtension, the issue seemed to be fixed(but its not like i did extensive testing). but with python.useEnvsExtension disabled and the extension itself enabled through the extension ui, it did seem to have an effect as i never got the issue if i just disabled the extension from the extension ui. dont know what exactly enabling it through the extensions ui(cntrl + shift + x) does vs in the settings tab(python.useEnvsExtension).

when i first tried debugging it, i ran this:

import time, signal, traceback

def handler(sig, frame):
    with open("signal_log.txt", "w") as f:
        f.write(f"Signal {sig} received\n")
        traceback.print_stack(frame, file=f)
    raise KeyboardInterrupt

signal.signal(signal.SIGINT, handler)

init = time.time()
while True:
    print(f"\r{time.time()-init}", end="", flush=True)

and the file it made contained this:
Signal 2 received
File "/home/dumbledore/CODE/Python/VSCODE SOURCE FILES/Programs/main.py", line 316, in
print(f"\r{time.time()-init}", end="", flush=True)
dont know if that helps

issue appears:

Terminal › Integrated › Shell Integration: Enabled = True
and
Extensions menu(cntrl + shift + x) > Python Environments = enabled
and
Python › Experiments: Enabled = False
and
Python: Use Environments Extension = False

issue doesnt appear:

the situation above, just:
Extensions menu(cntrl + shift + x) > Python Environments = disabled
or
Python: Use Environments Extension = True
or
Terminal › Integrated › Shell Integration: Enabled = False
or(only sometimes, so would i venture a guess this might just be incidental)
Python › Experiments: Enabled = True

ill be available from roughly 7am to 3pm UTC, though odds are ill still be available 'till much later

[eleanorjboyd]

The good news here is that the useEnvsExtension will become our default and it seems like that fixes the issue for you. I will pass this off to @anthonykim1 as he is our shell expert here but if Anthony doesn't see any issues we may just close this as out of scope since the new and improved experience is working

[anthonykim1]

Keyboard interrupt is because env extension is trying to activate terminal , but then it see your test.py running, so then it keyboard interrupts to reliably send activate command.

Shell startup would be the best approach for these scenarios which means you wont see activate command sent in terminal and we will still activate terminal upon launch so then your Python file execution does not get interrupted (at least via venv activate)

Please set python-envs.terminal.autoActivationType to shellStartup in your settings.
Also add "python.useEnvironmentsExtension": true, to your settings.json.

#962 will be the default once env extension rolls out fully.