You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VSCode allows A/B experiments in extensions via the vscode-tas-client package. Some experiments are enabled for all users on the TAS server but disabled by default in the client code.
One example is the pythonTestAdapter experiment in the Python extension, which enables a full rewrite of test-related functionality. See microsoft/vscode-python#17242 for a full list of the improvements. I don't believe the legacy test adapter has seen updates so we're effectively running unmaintained code.
Here's a tiny example, I'm sure there are worse side-effects. The legacy test adapter doesn't support colorized outputs:
Legacy:
Rewrite:
There may be other extensions running into a similar issue. I can think of two ways to deal with this:
Let each extension deal with it separately, and enable any required experiments as needed.
Override the module loader to patch vscode-tas-client to always return a "no-op" experimentation service that operates from a hard-coded list of enabled/disabled experiments (it could extend the TelemetryDisabledExperimentationService).
Host our own TAS server and configure vscode-tas-client to use that.
The text was updated successfully, but these errors were encountered:
For reference, here are the Python extension experiments I currently see enabled by the TAS server in VSCode:
2024-05-31 17:18:12.912 [info] Experiment 'pythonCreateEnvOnPipInstall' is active
2024-05-31 17:18:12.912 [info] Experiment 'pythonRecommendTensorboardExt' is active
2024-05-31 17:18:12.912 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2024-05-31 17:18:12.912 [info] Experiment 'pythonTestAdapter' is active
VSCode allows A/B experiments in extensions via the vscode-tas-client package. Some experiments are enabled for all users on the TAS server but disabled by default in the client code.
One example is the
pythonTestAdapter
experiment in the Python extension, which enables a full rewrite of test-related functionality. See microsoft/vscode-python#17242 for a full list of the improvements. I don't believe the legacy test adapter has seen updates so we're effectively running unmaintained code.Here's a tiny example, I'm sure there are worse side-effects. The legacy test adapter doesn't support colorized outputs:
Legacy:
Rewrite:
There may be other extensions running into a similar issue. I can think of two ways to deal with this:
vscode-tas-client
to always return a "no-op" experimentation service that operates from a hard-coded list of enabled/disabled experiments (it could extend theTelemetryDisabledExperimentationService
).vscode-tas-client
to use that.The text was updated successfully, but these errors were encountered: