Skip to content

🐛 upgrade agentic no-response logging from silly to warn#1391

Open
ibolton336 wants to merge 2 commits intokonveyor:mainfrom
ibolton336:fix/agentic-no-response-logging
Open

🐛 upgrade agentic no-response logging from silly to warn#1391
ibolton336 wants to merge 2 commits intokonveyor:mainfrom
ibolton336:fix/agentic-no-response-logging

Conversation

@ibolton336
Copy link
Copy Markdown
Member

Summary

Upgrades no-response logging from logger.silly() to logger.warn() in agentic workflow nodes. When the LLM returns no response (undefined), the previous silly level logging made it invisible in normal log output, making misconfigured model providers very hard to diagnose.

Changes

  • analysisIssueFix.tsAnalysisIssueFix and SummarizeHistory nodes now log at warn level with file name context
  • diagnosticsIssueFix.tsPlanFixes, FixGeneralIssues, FixJavaDependencyIssues nodes now log at warn level

All messages include "This may indicate a model provider configuration issue" to guide debugging.

Testing

  • No behavior change — only log level and message content
  • Existing tests unaffected

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>
@ibolton336 ibolton336 requested a review from a team as a code owner May 1, 2026 18:26
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 1, 2026

Warning

Rate limit exceeded

@ibolton336 has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 26 seconds before requesting another review.

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 @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 78605b67-3852-48c4-89f0-b450e9264503

📥 Commits

Reviewing files that changed from the base of the PR and between 3d97606 and f8c1409.

📒 Files selected for processing (3)
  • agentic/src/nodes/analysisIssueFix.ts
  • agentic/src/nodes/diagnosticsIssueFix.ts
  • changes/unreleased/1391-agentic-no-response-logging.yaml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests

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.

❤️ Share
Review rate limit: 0/1 reviews remaining, refill in 19 minutes and 26 seconds.

Comment @coderabbitai help to get the list of available commands and usage tips.

ibolton336 added a commit to ibolton336/editor-extensions that referenced this pull request May 1, 2026
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>
@ibolton336 ibolton336 changed the title fix: upgrade agentic no-response logging from silly to warn 🐛 upgrade agentic no-response logging from silly to warn May 1, 2026
ibolton336 added a commit to ibolton336/editor-extensions that referenced this pull request May 1, 2026
Signed-off-by: ibolton336 <ibolton@redhat.com>
@ibolton336 ibolton336 force-pushed the fix/agentic-no-response-logging branch from d2267cd to f8c1409 Compare May 1, 2026 18:58
ibolton336 added a commit to ibolton336/editor-extensions that referenced this pull request May 1, 2026
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant