Unable to opt out of experiments in a remote container
See original GitHub issueEnvironment data
- VS Code version: 1.53.2
- Extension version (available under the Extensions sidebar): v2021.2.582707922
- OS and version: Ubuntu 20.04
- Python version (& distribution if applicable, e.g. Anaconda): v3.9
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): N/A
Expected behaviour
Setting ""python.experiments.enabled": false"
or "python.experiments.outOptFrom": ["All"]
in my .code-workspace
file should opt out of all experiments. Several people on my team have complained about the pythonPath
changes but I wasn’t able to repro it. To keep us all on the same page and not have settings change randomly per user (since we source control the .code-workspace
file), I want to opt all of us out of all experiments.
Actual behaviour
Even with both settings stated above and restarting my VSCode instance I see the following in Python Output:
User belongs to experiment group 'pythonaacf'
User belongs to experiment group 'pythonJoinMailingListVar3'
User belongs to experiment group 'pythonjediLSP'
User belongs to experiment group 'pythonSendEntireLineToREPL'
User belongs to experiment group 'pythonNotDisplayLinterPrompt'
User belongs to experiment group 'pythonTensorboardExperimentcf'
User belongs to experiment group 'AlwaysDisplayTestExplorer - control'
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - enabled'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'AA_testing - experiment'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'CollectLSRequestTiming - control'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
User belongs to experiment group 'EnableIPyWidgets - experiment'
User belongs to experiment group 'DeprecatePythonPath - control'
User belongs to experiment group 'RunByLine - experiment'
User belongs to experiment group 'CustomEditorSupport - control'
Additionally, the "python.experiments"
settings block does not auto-complete/suggest in Workspace or User settings.
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Unable to run systemd services on Docker Desktop 4.3.0 #6073
I have tried with the latest version of Docker Desktop I have tried disabling enabled experimental features I have uploaded Diagnostics ...
Read more >Change preferences on Mac - Docker Documentation
Change preferences on Mac. This page provides information on how to configure and manage your Docker Desktop settings. To navigate to Preferences either:....
Read more >Interactive debugging with Visual Studio Code - Microsoft Learn
Interactively debug Azure Machine Learning code, pipelines, and deployments using Visual Studio Code.
Read more >Visual Studio Code Frequently Asked Questions
VS Code uses experiments to try out new features or progressively roll them ... The VS Code product notifies all users that they...
Read more >How to use Podman inside of a container | Enable Sysadmin
Podman-remote in rootful Podman with a leaked Podman socket from the host. # podman run -v /run:/run --security-opt label=disable quay.io/podman ...
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 FreeTop 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
Top GitHub Comments
🤦 Now it’s recognized.
So our workspace is running in a remote container. I initially tried to opt out in Workspace and User settings; neither worked.
I just tried in the Remote settings (
container::/home/dan/.vscode-server/data/Machine/settings.json
) and"python.experiments.enabled": false
appears to work but was not offered as a suggestion while typing."python.experiments.outOptFrom": ["All"]
is greyed out and claims to be unrecognized.I know that there’s a lot more nuanced debate happening about the experiment on the main thread but since we do source control our Workspace settings, it feels bad when an experiment that we can’t control forcefully changes our shared config for some team members without a warning or notification that it happened.
Deprecation of settings is fine, and VSCode has a mechanism for warning/squiggly-lining those settings. Forced change for only some users is not cool.