[Targeting] Windows launch-on-login - #16433
Conversation
0aff14a to
83aebef
Compare
|
I'm not sure why the tests are complaining about this one, since it's existed for quite some time. The other one is new and just landed in Nightly. |
|
@aminomancer Oh I see, it's added here: but not here: which is required to be targetable by Nimbus: https://experimenter.info/platform-guides/desktop/targeting#adding-new-targeting-options If you added it to the Nimbus targeting context it'll get picked up on the next sync then this should pass 👍 |
|
@jaredlockhart Thanks, I've added a patch for this. We'll try to remember that in the future. Is this required by the Nimbus client to even do the client-side targeting, or is it only required for these tests to pass? I'm looking at the code in RemoteSettingsExperimentLoader, and it seems like it's just directly using ASRouterTargeting for targeting. This targeting config is intended for an experiment that would target 153.0.1 (the dot release). So I'm wondering whether we need to uplift that patch I linked. It doesn't seem like it, but it would be good to confirm. If Experimenter only cares what's on Nightly, then we shouldn't need to uplift it. But maybe Experimenter will throw an error if we combine a min version of 153.0.1 with an advanced targeting config that uses attributes that only exist on 155, and then I guess we'd need to uplift the attributes. |
|
@aminomancer Perfect here it is: And yes so right now only Experimenter is validating against that list but soon desktop will soon as well so better to get it all in place now rather than getting caught out when the client makes the switch. After the above lands we can update this and it should be passing 🙏 |
0f342f2 to
e0f3d63
Compare
|
@aminomancer Okay all tidied up, I'll mark it as blocked so it doesn't get accidentally merged until you're ready. |
cc88aac to
34ad1d1
Compare
4927cdd to
babb0f6
Compare
Fixes #16432