Environment created in terminal while in restricted mode not detected when entering trusted mode
See original GitHub issue- Start in restricted mode
- Create and open a Python file
python -m venv .venv
in the terminal- Leave restricted mode
- Notice how the newly created virtual environment is not automatically selected
Issue Analytics
- State:
- Created a year ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Visual Studio Code Workspace Trust security
Opening in Restricted Mode is the safest option and you can always reopen the file in your original VS Code window once you...
Read more >What is 'Restricted mode' in the VS Code status bar and how ...
Hit CTRL + SHIFT + P (or your local equivalent) to open the Command Palette. Start typing Workspaces: Manage Workspace Trust and select...
Read more >Environments and deployments - GitLab Docs
While there is no technical reason not to use a name like customer-portal , the name no longer ... GitLab can open a...
Read more >Set-ExecutionPolicy (Microsoft.PowerShell.Security)
The Set-ExecutionPolicy cmdlet is available, but PowerShell displays a console message that it's not supported. An execution policy is part of the ...
Read more >Trusted execution environment - Wikipedia
Intel SGX allows user-level code to allocate private regions of memory, called enclaves, which are designed to be protected from processes running at...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Btw, if no interpreter has previously been selected for the workspace, we should ideally automatically select the local
.venv
once it is trusted.That definitely wasn’t the case. It may be that not being able to open a terminal in untrusted mode changed and so this isn’t feasible anymore. I’m going to close as outdated and worry about it if I come across it again.