🐛 Fixes Respect Keyboard interrupt #776

[jwmatthews]

Fix Ctrl-C lockup during analysis (#776)

kantra analyze hangs when Ctrl-C is pressed during rule processing,
provider startup, or provider preparation. Multiple independent bugs
prevent signal context cancellation from propagating to blocking
operations.

analyzer-lsp fixes:

• Buffer engine response channel so workers don't block after handler exits
• Guard rule dispatch loop with ctx.Done() to prevent deadlock on full channel
• Buffer ProviderStart abConfigChan and add ctx.Done() to init wait select
• Add 5s timeout to gRPC provider Stop() (was context.TODO() with no timeout)
• Thread context through GetProviderClient/NewGRPCClient for signal-aware startup
• Rewrite checkServicesRunning to accept context and fix broken 30s timeout

kantra fixes:

• Return immediately after cancelled analysis, skip post-analysis work
• Use fresh 30s timeout context for env.Stop() cleanup instead of cancelled signal context
• Add dedicated signal channel for interrupt feedback and second Ctrl-C force-exit

Co-Authored-By: Claude Opus 4.6 (1M context) noreply@anthropic.com

fixes #776

Dependent on konveyor/analyzer-lsp#1133

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 2bc7b8be-3473-419f-b51d-d1e984646d2c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ 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

• X
• Mastodon
• Reddit
• LinkedIn

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

[codecov]

Codecov Report

❌ Patch coverage is 0% with 24 lines in your changes missing coverage. Please review.
✅ Project coverage is 49.67%. Comparing base (adf348d) to head (0938958).
⚠️ Report is 38 commits behind head on main.

Files with missing lines	Patch %	Lines
cmd/analyze/analyze.go	0.00%	17 Missing ⚠️
cmd/analyze/run.go	0.00%	7 Missing ⚠️

❌ Your patch check has failed because the patch coverage (0.00%) is below the target coverage (80.00%). You can increase the patch coverage or adjust the target coverage.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #777      +/-   ##
==========================================
- Coverage   49.93%   49.67%   -0.26%     
==========================================
  Files          53       53              
  Lines        4474     4497      +23     
==========================================
  Hits         2234     2234              
- Misses       1966     1989      +23     
  Partials      274      274              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[github-actions]

This pull request has been automatically marked as stale because it has not had any activity for 60 days.
It will remain open for visibility and reporting purposes.
Please comment if this PR is still relevant.