Use same logic to disable normandy as other test harnesses (ie set a localhost URL for it)
Categories
(Remote Protocol :: Agent, task, P3)
Tracking
(Not tracked)
People
(Reporter: Gijs, Unassigned)
Details
Noticed in bug 1814884, specifically https://phabricator.services.mozilla.com/D174039#inline-964327 .
Comment 1•1 year ago
|
||
So this is about the app.normandy.api_url
preference that we currently set to an empty string in geckoinstance.py and in RecommendedPreferences.sys.mjs.
Under testing/profiles the preference is set to a value like https://127.0.0.1/selfsupport-dummy/
.
I wonder if that actually needs a valid page or can just be a dummy (non-existing) page. Searching for selfsupport-dummy
doesn't actually reveal any static page nor a handler for such URL. Or might it be even better when we disable the feature by default via app.normandy.enabled
?
Barret, what would be your advice? Thanks.
Updated•1 year ago
|
Comment 2•1 year ago
|
||
If you actually want to disable normandy, the pref is probably the best way to go.
Comment 3•11 months ago
|
||
Hi Barret. Regarding the app.normandy.enabled
preference. Can it be set during startup of Firefox or would it be better to set it for the profile before Firefox actually starts? I wonder when it will be the first time the feature is accessed after starting Firefox.
Comment 4•11 months ago
|
||
Normandy is initialized quite early on before UI startup in BrowserGlue. The following is a stack trace to the first read of the pref:
https://searchfox.org/mozilla-central/source/browser/components/BrowserGlue.sys.mjs#1338
https://searchfox.org/mozilla-central/source/toolkit/components/normandy/Normandy.sys.mjs#86
https://searchfox.org/mozilla-central/source/toolkit/components/normandy/Normandy.sys.mjs#173
https://searchfox.org/mozilla-central/source/toolkit/components/normandy/lib/RecipeRunner.sys.mjs#201
https://searchfox.org/mozilla-central/source/toolkit/components/normandy/lib/RecipeRunner.sys.mjs#92
Description
•