Preventing Terminal Trust prompt #24770
Comments
|
we are using the |
|
To reproduce, create a workspace that is not trusted. With an external file manager, create a file inside that workspace that requests a terminal to be spawned - in my case that is a Python file, but that is likely due to something the Python extension does. When that file is opened in VSCode, the above popup always appears and no setting I have tried can silence it. |
|
Just following up on this briefly; is this recognized as an issue and reproducible? Do you need anything else from my end? |
|
What is the file that is causing the terminal to show automatically on startup? How can I reproduce that? |
|
You can reproduce this as follows. Create a folder that is not trusted by VSCode, I will assume this location: Install the Python and Pylance extensions, and add the following to your VSCode settings: "extensions.supportUntrustedWorkspaces": {
"ms-python.python": {
"supported": true,
},
"ms-python.vscode-pylance": {
"supported": true,
},
}Create a file named Open the folder in VSCode. Inside VSCode, open the file |
|
Ah, I see, you force override the Python extensions to run in an untrusted workspace. While we support you doing this, it is not a supported flow. This is a feature request on the python extensions to support untrusted workspaces and live with some features disabled. @luabud @karthiknadig |
|
@sbatten Python extension already supports running in untrusted workspace to provide completions, features like code execution, Testing, REPL, etc are disabled in this mode. I think the user ask here is about the popups and notifications from core when opening untrusted workspaces. |
That is correct. |
|
Just checking in, are there any updates here? Should I do something? |
|
@karthiknadig if you support running in an untrusted mode, then I don't think you should be auto-triggering any actions which require workspace trust. That seems to be the cause of the dialogs. |
|
Dear @karthiknadig, as explained here, this happens as soon as I open a Python file. |
|
I apologize for missing that. Moving this to Python repo for further investigation. |
github-actions
bot
added
the
triage-needed
|
Here's my monthly check-in; do you need anything from me? =) |
|
Hey @karthiknadig, what is the next action on this ticket? Can I assist you in any way? |
|
@jhhcs We need to see what exact thing is triggering a terminal run. The next step is enabling trace logs for python and then looking at the logs to seeing what the extension tries to run. If you can please collect and share those logs. |
github-actions
bot
added
the
info-needed
|
I tried my best to figure out how to enable trace logs for Python, but failed. Could you tell me what to do exactly? |
github-actions
bot
removed
the
info-needed
|
Use the "Developer: Set Log Level ..." command:
There you can set it to "Trace" for all extensions or specifically for Python. Clicking on the ✔️ button will preserve it between loads.
|
|
I am sorry for being unclear @karthiknadig, this part didn't give me so much trouble - I cannot figure out where to find the logs. They are not shown under "Output" as some web searches led me to believe and I do not know where they would be stored on disk. |
|
Nevermind. There's a "Show Logs" command 🤦 |
|
I set the debug level to trace, cleared all the logs, opened a file and was prompted (as usual). The only log entries that were added were the following: Window Python Test Log Git |
|
Was there anything in the Output > Python logs? It is strange that there was the test logs but not Python logs. |
github-actions
bot
added
the
info-needed
|
I don't really know why I didn't get this in my previous test, but I just did it again and got a lot more logs: Python Python Language Server Terminal |
github-actions
bot
removed
the
info-needed
karthiknadig
added
bug
System
Description
When I open some files in an untrusted workspace, the following banner pops up:
Transcribed for searchability:
I would like to request the ability to disable this pop-up. To clarify, I very much want to keep the workspace untrusted and I very much want to prevent the creation of a terminal session, I just don't want to be prompted about it. I have the following settings enabled already:
{ "security.workspace.trust.startupPrompt": "never", "security.workspace.trust.banner": "never", }but neither achieves the desired result.
In a recent session, this banner actually became a potential security risk; as I had assumed to be rid of the banner, I started typing immediately after opening the file. I happened to press Space in the exact moment that this banner popped up, confirming the default selection to trust the workspace, which was absolutely not what I intended.
The text was updated successfully, but these errors were encountered: