Summary: | Caches::initialize should call all pending initialization callbacks in case of error | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | youenn fablet <youennf> | ||||||||
Component: | Service Workers | Assignee: | youenn fablet <youennf> | ||||||||
Status: | RESOLVED FIXED | ||||||||||
Severity: | Normal | CC: | achristensen, cdumez, cgarcia, commit-queue, ews-watchlist, rniwa, webkit-bug-importer | ||||||||
Priority: | P2 | Keywords: | InRadar | ||||||||
Version: | WebKit Nightly Build | ||||||||||
Hardware: | Unspecified | ||||||||||
OS: | Unspecified | ||||||||||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=183068 | ||||||||||
Attachments: |
|
Description
youenn fablet
2018-02-22 13:54:33 PST
Created attachment 334476 [details]
Patch
Created attachment 334477 [details]
Patch
Created attachment 334478 [details]
Patch
Comment on attachment 334478 [details] Patch Clearing flags on attachment: 334478 Committed r228936: <https://trac.webkit.org/changeset/228936> All reviewed patches have been landed. Closing bug. Why didn't this patch have tests? (In reply to Ryosuke Niwa from comment #7) > Why didn't this patch have tests? These errors typically happen when there is a failure to read or write from disk. We do not have a way to emulate or trigger these errors. In addition, this is time sensitive since the app needs to try opening the same Caches twice from different frames/tabs at the same time to face that issue. |