fix(privacy): rebuild bounded ETL failure logging on live develop - #320
Conversation
|
Warning Review limit reached
Next review available in: 40 minutes You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
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 |
Replacement for stale-base #219, rebuilt from exact protected
develop@8f96517987cf2cab4398696503b22a131a4b66a6without rewriting historical evidence. Commit5ec41b1001a03c5f8c85ab0c5ec1bc9676b526acis test-only RED: it adds the focused logging contract while the production handler remained the exact protected blob6ab4ff3e7a5ba190dfdf602c5b0710b61710453a, whose real log statements interpolaterequest.getRequestURI()into the captured target-failure line. Commit64d186351704ab6993343a5a8dc9b16f73501029is the narrow GREEN candidate: it removes request-resource identity from the five ordinary handler log calls while preserving RFC 9457ProblemDetail.instance, stable classifications, exception-type metadata, routing, authorization and response semantics. The two resulting files preserve #219's unique source/test blobs exactly. Old checks/reviews do not transfer; fresh exact-head validation is required. No masking, hashing, gate weakening, force-push or cross-repository mutation.