Fix/skip rabbitmq integration without broker#119
Conversation
- AnalysisAiClient formatted prompt의 점수 가중치 퍼센트 값을 %%로 escape - STATUS_AND_WRITING_RULES의 X% 예시도 formatter-safe하게 수정 - AnalysisServiceTest로 컴파일 및 분석 흐름 회귀 검증
- RabbitPublishSupportIntegrationTest 실행 전 localhost:5672 연결 가능 여부 확인 - RabbitMQ가 없는 CI clean test 환경에서는 JUnit assumption으로 테스트 skip - RabbitMQ가 준비된 환경에서는 기존 publisher confirm/return 통합 테스트 유지 - ./gradlew --no-daemon clean test 통과 확인
|
Warning Review limit reached
Next review available in: 33 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: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
✨ 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 |
✨ 어떤 이유로 PR를 하셨나요?
📋 세부 내용 - 왜 해당 PR이 필요한지 작업 내용을 자세하게 설명해주세요
📸 작업 화면 스크린샷
🚨 관련 이슈 번호 [ ]