Use only one RemoteSetting instance for all URL Classifier features
Categories
(Toolkit :: Safe Browsing, task)
Tracking
()
Tracking | Status | |
---|---|---|
firefox76 | --- | fixed |
People
(Reporter: dimi, Assigned: dimi)
References
Details
Attachments
(1 file, 3 obsolete files)
We should be able to use the same RemoteSetting instance for all the URL Classifier features. Besides that, we should also avoid syncing remote setting data for every features (See Bug 1617971 Comment 4)
Assignee | ||
Comment 1•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Updated•5 years ago
|
Comment 3•5 years ago
|
||
Comment 6•5 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/cffc27728f9e
https://hg.mozilla.org/mozilla-central/rev/0dc7fbadfe15
Comment 7•5 years ago
|
||
This is getting backed out for causing bug 1627377. This is because I missed the fact that not all features get created immediately when the service initializes, and when features get created later, they get no initial data and so never properly initialize. I'll put up a combined patch that addresses this and request review.
Updated•5 years ago
|
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Backed out for causing Bug 1627377.
Failure log: https://treeherder.mozilla.org/logviewer.html#?job_id=296192718&repo=autoland
Backout link: https://hg.mozilla.org/integration/autoland/rev/890c9bc949ba110737e6d15804fb282705972f8e
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - TEST-PASS | toolkit/components/antitracking/test/browser/browser_siteSpecificWorkArounds.js | callbackAfterRemoval must be passed when accessRemoval is non-null -
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - Waiting for the skip list service to initialize...
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - Buffered messages finished
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - TEST-UNEXPECTED-FAIL | toolkit/components/antitracking/test/browser/browser_siteSpecificWorkArounds.js | Uncaught exception - Skip list service initialized - timed out after 50 tries.
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - Leaving test bound
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - Entering test bound
[task 2020-04-04T11:43:38.176Z] 11:43:38 INFO - Cleaning up.
[task 2020-04-04T11:43:38.317Z] 11:43:38 INFO - Leaving test bound
[task 2020-04-04T11:43:38.318Z] 11:43:38 INFO - Entering test bound
[task 2020-04-04T11:43:38.319Z] 11:43:38 INFO - Starting non-blocking cookieBehavior (0) without allow list test localStorage with a tracker that is whitelisted via a pref running in a normal window with iframe sandbox set to null and access removal set to null
[task 2020-04-04T11:43:38.319Z] 11:43:38 INFO - TEST-PASS | toolkit/components/antitracking/test/browser/browser_siteSpecificWorkArounds.js | callbackAfterRemoval must be passed when accessRemoval is non-null -
[task 2020-04-04T11:43:38.359Z] 11:43:38 INFO - Waiting for the skip list service to initialize...
[task 2020-04-04T11:43:43.479Z] 11:43:43 INFO - Not taking screenshot here: see the one that was previously logged
Comment 9•5 years ago
|
||
Backout merged: https://hg.mozilla.org/mozilla-central/rev/890c9bc949ba
Comment 10•5 years ago
|
||
Assignee | ||
Comment 11•5 years ago
|
||
Assignee | ||
Comment 12•5 years ago
•
|
||
hi gijs,
Thank you for your help and sorry for not thinking and testing carefully while working on this.
I didn't realize that you already have a patch reviewed while working on my fix yesterday.
I wrote testcases anyway, maybe we can still use that part.
Comment 13•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Description
•