[Fix] Cohere 임베딩 클라이언트 풀링 및 재시도 적용 - #228
Conversation
- CohereCorpusEmbeddingClient를 global CohereEmbeddingClient 위임 구조로 변경 - cohere.api-key/base-url/embedding 설정으로 Cohere 설정 통합 - corpus embedding 모델 참조를 CohereProperties 기준으로 정리 - 기존 pgvector 저장 및 similarity search 구조는 유지 - Cohere corpus 위임 테스트 보강
- CohereEmbeddingClient에 HttpClient5 connection pool 적용 - 429/5xx 응답에 bounded exponential backoff 재시도 추가 - Retry-After 헤더 기반 대기 처리 - readTimeout 예외 매핑 회귀 테스트 추가
|
Warning Review limit reached
Next review available in: 44 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: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (13)
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이 필요한지 작업 내용을 자세하게 설명해주세요
📸 작업 화면 스크린샷
🚨 관련 이슈 번호 [ ]