|Submitter||Diff||Changes||Open Issues||Last Updated|
|Error loading review requests:|
Initially we shipped a static DLC catalog in the app. This allowed us to immediately download without synchronizing the catalog first. And more importantly: We could ship DLC without waiting for Kinto to be available in production. Now because of bug 1382596 we see a bunch of clients in the wild with an invalid catalog causing a bunch of 404 request on CDN side. I think it's time to retire this bootstrap catalog - it is hard (or impossible) to pull a catalog that we shipped in the app. We have Kinto in production for some time now and we see that the sync of it is working.
Jason: Even with removing this bootstrap catalog we will see some clients hit those URLs for a long time. I guess somehow re-activating those URLs is not really feasible?
(In reply to Sebastian Kaspari (:sebastian) from comment #1) > Jason: Even with removing this bootstrap catalog we will see some clients > hit those URLs for a long time. I guess somehow re-activating those URLs is > not really feasible? Kinto records for fennec objects provides two hashes one for the gzipped content and another for the original content. Does fennec client use both of these hashes to validate the object? If fennec client doesn't validate the gzipped object hash then I think it would be straight forward to create new objects and put them in S3. If fennec client uses both hashes it would be more complicated. One of the issues is that gzip metadata will alter the hash of the gzipped object, specifically I think mtime of the original object is the culprit. Assuming that is the only issue we could try to manipulate the mtime during gzip object creation but it would be essentially be a brute force operation.
Comment on attachment 8892967 [details] Bug 1386305 - (DLC) Remove outdated bootstrap catalog. https://reviewboard.mozilla.org/r/163974/#review169512 I'm not too familiar with this code but this seems reasonable to me. (note: your try failure is a presumably unrelated failure in testDSAGeneration (or whatever)).
Pushed by firstname.lastname@example.org: https://hg.mozilla.org/integration/autoland/rev/92853fc3f060 (DLC) Remove outdated bootstrap catalog. r=mcomella
Comment on attachment 8892967 [details] Bug 1386305 - (DLC) Remove outdated bootstrap catalog. Approval Request Comment [Feature/Bug causing the regression]: We ship a catalog of downloadable content (fonts) inside the app. This catalog is outdated. As we are synchronizing this data from a Kinto server this static catalog isn't needed anymore. [User impact if declined]: The clients are trying to download from a URL that only returns 404 errors. The clients will fix themselves after they updated the local catalog. However the 404 errors are showing up in our CDN monitoring an make it hard to look out for actual problems. [Is this code covered by automated tests?]: It's covered by a unit test and this patch modifies one of those tests accordingly. [Has the fix been verified in Nightly?]: I tested this patch with a local build. The catalog synchronizes nicely from Kinto (as it already does in all release channels) and then starts to download from the correct URLs. [Needs manual test from QE? If yes, steps to reproduce]: - [List of other uplifts needed for the feature/fix]: - [Is the change risky?]: Very Low [Why is the change risky/not risky?]: Instead of shipping a list of things to download we are starting with an empty catalog. [String changes made/needed]: -
Comment on attachment 8892967 [details] Bug 1386305 - (DLC) Remove outdated bootstrap catalog. Sounds like this is not considered risky. Let's try it for beta 1.