🐛 upgrade agentic no-response logging from silly to warn#1391
🐛 upgrade agentic no-response logging from silly to warn#1391ibolton336 wants to merge 2 commits intokonveyor:mainfrom
Conversation
When the LLM returns no response, log at warn level with actionable messages instead of silly level. Helps diagnose misconfigured model providers. Affected nodes: AnalysisIssueFix, SummarizeHistory, PlanFixes, FixGeneralIssues, FixJavaDependencyIssues Signed-off-by: Ian Bolton <ibolton@redhat.com>
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ How to resolve this issue?After the wait time has elapsed, 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 have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ 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. Review rate limit: 0/1 reviews remaining, refill in 19 minutes and 26 seconds.Comment |
The silly→warn logging upgrade is now in its own PR (konveyor#1391). Reverting to main versions to keep this PR focused. Signed-off-by: Ian Bolton <ibolton@redhat.com>
Signed-off-by: ibolton336 <ibolton@redhat.com>
d2267cd to
f8c1409
Compare
The silly→warn logging upgrade is now in its own PR (konveyor#1391). Reverting to main versions to keep this PR focused. Signed-off-by: Ian Bolton <ibolton@redhat.com>
Summary
Upgrades no-response logging from
logger.silly()tologger.warn()in agentic workflow nodes. When the LLM returns no response (undefined), the previoussillylevel logging made it invisible in normal log output, making misconfigured model providers very hard to diagnose.Changes
analysisIssueFix.ts—AnalysisIssueFixandSummarizeHistorynodes now log at warn level with file name contextdiagnosticsIssueFix.ts—PlanFixes,FixGeneralIssues,FixJavaDependencyIssuesnodes now log at warn levelAll messages include "This may indicate a model provider configuration issue" to guide debugging.
Testing