Repository navigation
feat: extract approval interaction service - #466
Conversation
|
Warning Review limit reached
More reviews will be available in 51 minutes and 36 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR extracts approval interaction persistence and resolution from ChangesApproval Interaction Service Extraction
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 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 |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@coding-agent/src/coding_agent/approval/interactions.py`:
- Around line 88-106: In resolve(), ensure the stored interaction key is derived
from the response rather than blindly using the standalone request_id: compare
the incoming request_id param with response.request_id and if they differ raise
an error (or replace request_id with response.request_id), then call
self.store.resolve_agent_interaction(...) using
approval_interaction_id(response.request_id, request_id) — or simply
approval_interaction_id(response.request_id, ...) — so the persisted payload
maps to the same request ID in response; update the resolve() implementation
(function resolve, symbols: ApprovalInteractionSession.current_turn_id,
approval_interaction_id, approval_interaction_status, approval_response_payload)
to perform this validation and use the validated/derived request_id.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro Plus
Run ID: 78f3dd29-858f-45c7-bf6c-c6f5f97bf19e
📒 Files selected for processing (6)
coding-agent/.opencode/prompts/tasks/local-daemon-pr43-approval-interaction-service.mdcoding-agent/docs/adr/0058-local-daemon-control-plane-executor-architecture.mdcoding-agent/src/coding_agent/approval/__init__.pycoding-agent/src/coding_agent/approval/interactions.pycoding-agent/src/coding_agent/server/session_manager.pycoding-agent/tests/coding_agent/test_approval_interactions.py
|
Local review fallback because CodeRabbit remained stuck in Reviewer: Lagrange ( Scope reviewed: Verification already run locally by implementer:
|
|
Final local review fallback after review-fix commit because the new CodeRabbit cycle emitted a rate-limit comment despite a passing status. Reviewer: Lagrange ( Verification after fix:
|
Summary
Verification
Summary by CodeRabbit
Refactor
Tests