`personality-provider` and `activity-stream.discovery_stream.json` are created in Root Directory
Categories
(Toolkit Graveyard :: OS.File, defect, P3)
Tracking
(firefox-esr91 unaffected, firefox98 wontfix, firefox99 wontfix, firefox100 fixed)
Tracking | Status | |
---|---|---|
firefox-esr91 | --- | unaffected |
firefox98 | --- | wontfix |
firefox99 | --- | wontfix |
firefox100 | --- | fixed |
People
(Reporter: 6k64x4ma, Assigned: beth)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 file)
Steps to reproduce:
- Launch Firefox with a new profile.
- Wait until
personality-provider
andactivity-stream.discovery_stream.json
are created.
Actual results:
They are created in Local Directory until https://archive.mozilla.org/pub/firefox/nightly/2022/01/2022-01-31-21-28-43-mozilla-central/
They are created in Root Directory since https://archive.mozilla.org/pub/firefox/nightly/2022/02/2022-02-01-09-39-42-mozilla-central/
Expected results:
I think they should be created in Local Directory.
Maybe this is regressed by Bug 1746667?
Assignee | ||
Updated•3 years ago
|
Assignee | ||
Comment 1•3 years ago
|
||
This was not caught in tests because in a test both ProfD and ProfLD will map
to the same directory (e.g., on Windows they both map to
C:\Users\<username>\AppData\Local\Temp\<random>.mozrunner).
Assignee | ||
Comment 2•3 years ago
|
||
We only have two consumers of PathUtils.getLocalProfileDir
: PersistentCache.jsm [1, 2] and PersonalityProviderWorkerClass.jsm [3]. I checked with :thecount and this will only result in us a) re-creating the discovery stream cache and b) re-running the personality provider worker, so I don't think this warrants an uplift.
Comment 4•3 years ago
|
||
bugherder |
Comment 5•3 years ago
|
||
Set release status flags based on info from the regressing bug 1746667
Updated•3 years ago
|
Updated•3 years ago
|
Updated•2 years ago
|
Description
•