User belongs to all controls in experiment

[DonJayamanne]

Here's my output from Python output panel:

User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'ShowExtensionSurveyPrompt - control'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'LS - control'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'WebHostNotebook - control'
User belongs to experiment group 'LocalZMQKernel - experiment'
User belongs to experiment group 'LocalZMQKernel - control'
User belongs to experiment group 'NativeNotebook - experiment'
User belongs to experiment group 'NativeNotebook - control'
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 'RunByLine - control'

As you can see I belong to the experiment and control group for two experiments LocalZMQKernel & NativeNotebook.

Here's my settings.json file

	"python.experiments.optInto": [
		"LocalZMQKernel - experiment",
		"NativeNotebook - experiment"
	],

I think we need to first check the opted in exepriments & then process the other list, and track the user experiments based on the experiment salt. This way they cannot belong to both control and experiment.
Also, we need to ensure opt in experiment takes precedence.

[karthiknadig]

/cc @karrtikr If I remember correctly this is a logging issue. As for the experiment, the priority is given to python.experiments.optInto. So you belong to that experiment. This is a known issue with the logging.

[DonJayamanne]

This is a known issue with the logging.

No, its not an issue with logging, the user is actually added into both experiment groups.
I have a fix ready.