Repository navigation
Ruby - Change the exit code to 130 - #303
Conversation
There was a problem hiding this comment.
🟡 Changes recommended
The Ctrl-C regression test does not assert Ruby’s exit status of 130, allowing a regression to status 0 to pass, and the README still documents that the status is unchecked.
1 open issue
What changed in this PR
Aligns the Ruby MCP client’s Ctrl-C exit status with the other four clients, completing the follow-up to #302 and #301.
Changes:
- Exits with status 130 when handling
Interrupt. - Preserves backtrace suppression and the existing
ensurecleanup path.
| File | Description |
|---|---|
mcp-client-ruby/client.rb |
Adds exit 130 to the Ctrl-C handler. |
Review effort: Balanced
olaservo
left a comment
There was a problem hiding this comment.
Thanks for picking up the follow-up. exit 130 raises SystemExit, so the ensure cleanup still runs, and Ruby now matches the other four clients. Checking for a non-zero status in the Ctrl-C test is a reasonable choice given that uv run reports a SIGINT death as 2, and it does catch a return to status 0. CI is green. Merging.
Generated by Claude Code

Motivation and Context
Follow-up to #302, as suggested in #301: after Ctrl-C the Ruby client exited with status 0, while the other four clients exit 130. It now exits 130 too.
ensurestill runs, so the server is still shut down.Closes #301
How Has This Been Tested?
Locally with Ruby 4.0.
Breaking Changes
N/a
Types of changes
Checklist
Additional context
Assisted by Claude Opus 5.5