fix(analytics): reject invalid KPI numeric evidence - #389
Closed
seonghobae wants to merge 2 commits into
Closed
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughKPI snapshot ledger가 ChangesKPI 증거 값 검증
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
seonghobae
marked this pull request as ready for review
August 11, 2026 17:09
seonghobae
enabled auto-merge (squash)
August 11, 2026 19:40
auto-merge was automatically disabled
August 12, 2026 09:36
Pull request was closed
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
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.
Objective
Advance issue #329 by making persisted KPI evidence fail closed when a ledger line contains non-finite/out-of-range conversion rates or negative preview latency. Keep the public invalid-line failure controlled and free of persisted line contents.
Test-first state
This Draft starts intentionally RED at exact test-only head
533dffaa83b91c1859d1ffc668e12cac60388d2e, directly based on protectedmain55d7ae8647208e301f282350f076eeddaba61d11.KpiSnapshotLedgerTest.rejectsNonFiniteOrOutOfRangePersistedKpiEvidencerequires replay rejection forNaN, positive/negative infinity, rates outside[0,1], and negative p95 latency. Protected main currently delegates toDouble.parseDouble/Long.parseLong, so these structurally parseable invalid values are expected to reach the record instead of failing closed.Scope
Bounded data-integrity repair under #329. It does not change KPI denominator semantics (#327/#328), tenant-query isolation (#326/#342), canonical documentation owned by #305, or other analytics contracts.
Acceptance
Observe exact-head RED, apply the smallest parse-boundary validation, then require focused/full
mvn -B --no-transfer-progress verify, exact 100% owned production line/branch coverage, warning-free public Javadocs, CI/Security Scan/SAST/fuzz, zero valid unresolved findings, fresh exact-head/live-base identity, and qualifying independent approval where live protection requires it.Summary by CodeRabbit
버그 수정
테스트