Closed
Bug 1830056
Opened 2 years ago
Closed 1 month ago
Nimbus integration with Search Service can to set up experiments before the search service has initialised
Categories
(Firefox :: Search, defect, P3)
Firefox
Search
Tracking
()
RESOLVED
FIXED
136 Branch
People
(Reporter: standard8, Assigned: standard8)
References
Details
(Whiteboard: [snt-][fixed by bug 1883685])
I had a test experiment applied which was setting extra parameters on engines. When restarting with the experiment enabled I noticed the error below on the console.
This doesn't break initialisation, but looks like it could break the experimentation set-up around the default private engine work.
Error: Something tried to use the search service before it's been properly intialized. Please examine the stack trace to figure out what and where to fix it:
#ensureInitialized@resource://gre/modules/SearchService.sys.mjs:1255:15
get defaultPrivateEngine@resource://gre/modules/SearchService.sys.mjs:189:28
#checkNimbusPrefs@resource://gre/modules/SearchService.sys.mjs:3225:34
#nimbusSearchUpdated@resource://gre/modules/SearchService.sys.mjs:3198:27
_onFeatureUpdate@resource://nimbus/lib/ExperimentStore.sys.mjs:390:17
onUpdate@resource://nimbus/ExperimentAPI.sys.mjs:472:26
#addObservers@resource://gre/modules/SearchService.sys.mjs:3274:32
#init@resource://gre/modules/SearchService.sys.mjs:1332:25
async*init@resource://gre/modules/SearchService.sys.mjs:366:23
getDefault@resource://gre/modules/SearchService.sys.mjs:205:16
_updateURLBarPlaceholderFromDefaultEngine@chrome://browser/content/browser.js:3836:31
delayedStartupInit@chrome://browser/content/browser.js:3696:10
_delayedStartup@chrome://browser/content/browser.js:1871:19
EventListener.handleEvent*onLoad@chrome://browser/content/browser.js:1773:12
EventHandlerNonNull*@chrome://browser/content/browser.xhtml:116:39
Assignee | ||
Updated•2 years ago
|
Whiteboard: [snt-]
Updated•2 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SNT-657
Comment hidden (admin-reviewed) |
Assignee | ||
Comment 2•2 years ago
|
||
I think here, we should wait for this.init()
in nimbusSearchUpdated
.
We should also avoid the extra _maybeReloadEngines
- by only doing that if we are making an actual change in checkNimbusPrefs
.
Assignee | ||
Comment 3•1 month ago
|
||
Bug 1883685 has reworked this so that we're no longer using isEarlyStartup
and the main part of the search service no longer listens directly to Nimbus, hence this should no longer be a potential issue.
Assignee: nobody → standard8
Status: NEW → RESOLVED
Closed: 1 month ago
Depends on: 1883685
Resolution: --- → FIXED
Whiteboard: [snt-] → [snt-][fixed by bug 1883685]
Target Milestone: --- → 136 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•