Bugzilla

Hi Valentin,

Am I getting this issue right that there's a bug, *when and only when* an experiment's control branch sets the feature to a value, which is *different* from the value set for a rollout?

For example, if the prerequisite becomes `have an experiment that sets the feature “on” on the control branch and “off” on the treatment branch, and a rollout that sets the feature "off" for the opaqueResponseBlocking feature config` , we will still get unexpected results, right? 

That also means, if an experiment that sets the feature “on” on the single control branch, which is *the same* value that a rollout sets, we won't have a bug when the user unenrolls from an experiment. Right? I am asking for clarification because we are currently running a Nimbus experiment which has only a single-branch to set the ORB feature "on", while we are planning to land a patch to turn ORB on and ship to all users by default. After feature shipping, we will plan to end the single-branch experiment. And I assume "end the single-branch experiment" means the same as "users unenroll from the experiment". Therefore, I want to ensure and confirm, in our scenario, users will still have ORB on, after the experiment ends, because that's the default setting we deployed. Thank you.

Hi Valentin,

Am I getting this issue right that there's a bug, *when and only when* an experiment's control branch sets the feature to a value, which is *different* from the value set for a rollout?

For example, if the prerequisite becomes `have an experiment that sets the feature “on” on the control branch and “off” on the treatment branch, and a rollout that sets the feature "off" for the opaqueResponseBlocking feature config` , we will still get unexpected results, right? 

Also, what if our experiment has only a single control branch, but not like your prerequisites which have 2 branches? If an experiment that sets the feature “on” on the single control branch, which is *the same* value that a rollout sets, what is the testing result? I am asking for clarification because we are currently running a Nimbus experiment which has only a single-branch to set the ORB feature "on", while we are planning to land a patch to turn ORB on and ship to all users by default. After feature shipping, we will plan to end that single-branch experiment (setting ON). And I assume "end the single-branch experiment" means the same as "users unenroll from the experiment". Therefore, I want to ensure and confirm, in our scenario, users will still have ORB on, after that experiment ends, because that's the default setting we deployed. Thank you.

Hi Valentin,

Am I getting this issue right that there's a bug, *when and only when* an experiment's control branch sets the feature to a value, which is *different* from the value set for a rollout?

For example, if the prerequisite becomes `have an experiment that sets the feature “on” on the control branch and “off” on the treatment branch, and a rollout that sets the feature "off" for the opaqueResponseBlocking feature config` , we will still get unexpected results, right? 

Also, what if our experiment has only a single control branch, not like your prerequisites which have 2 branches? If an experiment that sets the feature “on” on the single control branch, which is *the same* value that a rollout sets, what is the testing result? I am asking for clarification because we are currently running a Nimbus experiment which has only a single-branch to set the ORB feature "on", while we are planning to land a patch to turn ORB on and ship to all users by default. After feature shipping, we will plan to end that single-branch experiment (setting ON). And I assume "end the single-branch experiment" means the same as "users unenroll from the experiment". Therefore, I want to ensure and confirm, in our scenario, users will still have ORB on, after that experiment ends, because that's the default setting we deployed. Thank you.