Abort operations for given directory lock ids
Categories
(Core :: Storage: Quota Manager, task, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox85 | --- | fixed |
People
(Reporter: janv, Assigned: janv)
References
(Blocks 1 open bug)
Details
Attachments
(10 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Currently, when an origin is being cleared we go through the directory locks which block the clear operation and collect clients which need to be notified with AbortOperations(aOrigin)
.
However, this aborts all operations for given origin. The clear operation can now only clear data for given persistence type or client type. So we need to abort operations for given directory locks (instead for given origin), otherwise we can end up aborting operations for storages which are not about to be cleared.
I want to convert OpenDirectory
to use MozPromise
instead of a custom listener and this bug needs to be done first
Finally, I plan to use MozPromise
for the asynchronous initialization methods, so if OpenDirectory
uses that too, we can probably chain all that in a nice way.
Assignee | ||
Comment 1•4 years ago
|
||
Assignee | ||
Comment 2•4 years ago
|
||
Client::AbortOperations no longer supports the case when an empty origin string
is passed (which was used to abort all operations).
Depends on D98343
Assignee | ||
Comment 3•4 years ago
|
||
These methods are only used in QuotaClient class, so they don't need to be global.
Depends on D98344
Assignee | ||
Comment 4•4 years ago
|
||
Depends on D98345
Assignee | ||
Comment 5•4 years ago
|
||
This is just a minor cleanup.
Depends on D98346
Assignee | ||
Comment 6•4 years ago
|
||
A minor cleanup
Depends on D98347
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 7•4 years ago
|
||
Depends on D98348
Assignee | ||
Comment 8•4 years ago
|
||
Depends on D98430
Assignee | ||
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Comment 10•4 years ago
|
||
Depends on D98345
Comment 11•4 years ago
|
||
bugherder |
Comment 12•4 years ago
|
||
Assignee | ||
Comment 13•4 years ago
|
||
This patch changes the way how we abort operations when clearing of data is
requested. Instead of aborting all operations for given origin, we now abort
all operations for given directory locks which are blocking clearing of data.
Depends on D98345
Assignee | ||
Updated•4 years ago
|
Comment 14•4 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/bad84766f83c
https://hg.mozilla.org/mozilla-central/rev/10736db2685a
https://hg.mozilla.org/mozilla-central/rev/de20363fdc0f
https://hg.mozilla.org/mozilla-central/rev/c7e3c04eb74e
Comment 15•4 years ago
|
||
The core patch has not yet landed, so reopening.
I want to convert OpenDirectory to use MozPromise instead of a custom listener and this bug needs to be done first
Finally, I plan to use MozPromise for the asynchronous initialization methods, so if OpenDirectory uses that too, we can probably chain all that in a nice way.
This is not yet done. It's not clear to me if you want to do this within this bug, or in separate bugs? In the former case, we probably still need leave-open here.
Assignee | ||
Comment 16•4 years ago
|
||
Yes, I prematurely removed the leave-open flag, sorry.
Updated•4 years ago
|
Comment 17•4 years ago
|
||
Comment 18•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Description
•