Re: [w3c/ServiceWorker] Maximum file size that cache should support (Issue #1770)

asutherland left a comment (w3c/ServiceWorker#1770)

I agree with @domenic that this should probably be addressed more broadly (probably in the [storage spec](https://storage.spec.whatwg.org/)?), but I do want to recognize 2 issues raised here:
1. It does seem likely for implementations to have bugs around `uint32_t` and `int32_t` thresholds and it would be great to have tests to help implementations identify these bugs.  It seems like this might be more consistent with spec language saying files of 4GiB + 1 bytes must be supported.
2. Tests that do a ton of I/O, especially creating large files, really are unpleasant for automated testing runs because they tend to take a long time, be flaky, and/or be very unpleasant surprises for developers when running them locally.  I know for Firefox/Gecko's automated quota testing about limits we adjust preferences so our quota limits are like ~10 MiB to test our logic, but that obviously won't shake out bugs that explicitly involve the maximum values of integer types.  Does/could WPT have a concept of smoke/acceptance testing tests that are only run much less frequently?  (I say that realizing that it's possible such tests would then never be run, defeating the point while also making people think there is test coverage...)

-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1770#issuecomment-2891680583
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1770/2891680583@github.com>