fix(jp): reject incomplete downloads and isolate APK updates - #5
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Review of #3 reproduced incomplete HTTP responses being cached as complete files and empty JP master manifests being reported as successful downloads. It also found that changing the APK without changing the CDN snapshot could reuse stale embedded bundles or collide with the default catalog label.
Validation: 1,202 local tests passed; 45 strict golden/object-export checks passed; 117 targeted download/catalog/export regressions passed; 66 workflow helper tests passed (3 external-fixture skips). Pyflakes, actionlint, whitespace and staged Gitleaks checks passed. All new failure cases use synthetic local fixtures.
#3 was merged while this review was in progress; this PR contains only the review fixes.