Stuck in Reactivating terminals... due to cached broken environment

[roblourens]

In my vscode-copilot workspace, I have this status bar spinner that never goes away

I see this in the Terminal log when the window starts

2024-10-11 15:06:11.602 [error] Exception occurred during xterm disposal [{}]
2024-10-11 15:06:11.608 [error] Exception occurred during xterm disposal [{}]
2024-10-11 15:06:11.609 [error] Exception occurred during xterm disposal [{}]

[Tyriar]

@meganrogge do you know what causes this status bar item to appear? I can't find it searching the main repo for that string.

[Tyriar]

@roblourens any ideas what could be adding this? Some extension?

[meganrogge]

this is coming from python, I see it pretty often too.

[karthiknadig]

@roblourens What type of environment are you using? can you enable tracing and share the logs from Output > Python Locator?

[karthiknadig]

This was a caching issue. The bug seems to be that we don't re-set extension selection after we detect that the environment is not usable. Re-setting would force the extension attempt to find environments and select the most relevant one.

Temporary solution: Use the command "Python: clear cache and reload"

[JarmoHu]

It might be related to my settings. For example, my old setting had "python.defaultInterpreterPath": "D:\ProgramData\miniconda3\python.exe". However, I later reinstalled Python in a different location, which is probably why this issue happens.