Skip to content

fix: restore ctrl+c handling in gigacode (fixes #111) - #309

Open
rohanranjan0902 wants to merge 1 commit into
rivet-dev:mainfrom
rohanranjan0902:fix-gigacode-ctrl-c
Open

rohanranjan0902 wants to merge 1 commit into
rivet-dev:mainfrom
rohanranjan0902:fix-gigacode-ctrl-c

Conversation

@rohanranjan0902

Copy link
Copy Markdown

Description

This PR fixes an issue where the gigacode CLI does not gracefully exit when Ctrl+C is pressed.

Root Cause: The Node.js wrapper script was executing the underlying Rust binary synchronously using execFileSync. This blocked the Node event loop and prevented signals like SIGINT from properly reaching the child process.

Changes:

  • Replaced execFileSync with asynchronous spawn.
  • Added explicit signal forwarding for SIGINT, SIGTERM, and SIGQUIT from the parent Node process to the child Rust process.
  • Ensured the parent process waits to exit until the child process completes its shutdown.

Fixes #111

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.

Ctrl+C does not exit Gigacode

1 participant