fix(a2a): redact error event messages - #97
Conversation
|
Warning Review limit reached
Next review available in: 21 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
d606a22 to
7e52085
Compare
9f01a2b to
796d6d3
Compare
796d6d3 to
064dbfb
Compare
Objective
Redact model-visible A2A agent error event messages for Phase2 redaction closure.
Completed Changes
sendErrorEventResponseError.Messagethrough the shared platform redactor.ResponseErrorfields such as type, code, and param.Validation
go test ./agent/a2aagentgo vet ./agent/a2aagentgit diff --checkKnown Risks / Limitations
sendErrorEvent; remaining Phase2 model-visible error or metadata surfaces should be audited in follow-up increments.Follow-up Work
sendErrorEventpaths.