Skip to content

fix(privacy): rebuild bounded ETL failure logging on live develop - #320

Merged
github-actions[bot] merged 2 commits into
developfrom
repair/etl-problem-log-resource-id-8f96517
Aug 13, 2026
Merged

fix(privacy): rebuild bounded ETL failure logging on live develop#320
github-actions[bot] merged 2 commits into
developfrom
repair/etl-problem-log-resource-id-8f96517

Conversation

@seonghobae

Copy link
Copy Markdown
Collaborator

Replacement for stale-base #219, rebuilt from exact protected develop@8f96517987cf2cab4398696503b22a131a4b66a6 without rewriting historical evidence. Commit 5ec41b1001a03c5f8c85ab0c5ec1bc9676b526ac is test-only RED: it adds the focused logging contract while the production handler remained the exact protected blob 6ab4ff3e7a5ba190dfdf602c5b0710b61710453a, whose real log statements interpolate request.getRequestURI() into the captured target-failure line. Commit 64d186351704ab6993343a5a8dc9b16f73501029 is the narrow GREEN candidate: it removes request-resource identity from the five ordinary handler log calls while preserving RFC 9457 ProblemDetail.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.

@coderabbitai

coderabbitai Bot commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@seonghobae, you've reached your PR review limit, so we couldn't start this review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2bb3fb27-742c-490f-a26a-a7dcf7396c6c

📥 Commits

Reviewing files that changed from the base of the PR and between 8f96517 and 64d1863.

📒 Files selected for processing (2)
  • etl-service/src/main/java/com/xtrmetl/etl/controller/EtlApiProblemHandler.java
  • etl-service/src/test/java/com/xtrmetl/etl/controller/EtlApiProblemHandlerLoggingTest.java

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@seonghobae
seonghobae marked this pull request as ready for review August 13, 2026 16:22
@github-actions
github-actions Bot merged commit 2f9ed2f into develop Aug 13, 2026
35 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant