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
Check your hash (see @karrtikr 's comment) and salt and see which experiment(s) you belong to (in my case I had LS - enabled and AlwaysDisplayTestExplorer - enabled)
Go to settings and un-check 'Telemetry: Enable Telemetry' (or set telemetry.enableTelemetry to false)
Start debugging the extension inside a container and notice that the breakpoint is being hit
Logs
Output for Python in the Output panel after disabling telemetry:
User belongs to experiment group 'LS - enabled'
User belongs to experiment group 'AlwaysDisplayTestExplorer - enabled'
Starting Microsoft Python language server.
A/B testing issue: #5042
Environment data
"python.jediEnabled"set to; more info How to update the language server to the latest stable version #3977): JediExpected behaviour
Opting out of telemetry opts out of A/B testing, even if the local
experiments.jsonis populated.Actual behaviour
Opting out of telemetry doesn't prevent the local
experiments.jsonfile from being read and enabling experiments for the user.Steps to reproduce:
experiments.jsonwith:[ { "name": "LS - control", "salt": "LS", "min": 0, "max": 10 }, { "name": "LS - enabled", "salt": "LS", "min": 85, "max": 100 }, { "name": "AlwaysDisplayTestExplorer - enabled", "salt": "LS", "min": 70, "max": 90 }, { "name": "AlwaysDisplayTestExplorer - control", "salt": "LS", "min": 40, "max": 50 } ]LS - enabledandAlwaysDisplayTestExplorer - enabled)telemetry.enableTelemetrytofalse)experiments.tsLogs
Output for
Pythonin theOutputpanel after disabling telemetry: