CommandCodeAI / CommandCodeAI/command-code
Uncaught error for terminal command
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 4k
- Forks
- 350
- PR merge metrics
- No merged PRs in 30d
Description
Summary
✖ CRITICAL: Uncaught Exception!
This is an unexpected error. Please file a bug report at https://github.com/CommandCodeAI/command-code/issues/new
✖ ERROR → TypeError
ℹ REASON → Unknown signal: SIGTSTP
ℹ ERROR STACK ↓
TypeError [ERR_UNKNOWN_SIGNAL]: Unknown signal: SIGTSTP
at process.kill (node:internal/process/per_thread:230:15)
at Timeout._onTimeout (file:///C:/Users/Username/AppData/Roaming/npm/node_modules/command-code/dist/index.mjs:295:109456)
at listOnTimeout (node:internal/timers:588:17)
at process.processTimers (node:internal/timers:523:7)
ℹ Request ID: req_cfb7bdb69e0d63b848e3763255355907
Share this ID with support to help debug your issue.
Just pasted the log here. Using 0.30.2 on Windows 11.
Expected Behavior
No crash
Actual Behavior
Crash
Steps to reproduce the issue
Command Code Version
0.30.2
Operating System
Windows
Terminal/IDE
No response
Shell
No response
Additional context
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the timeout around line 295 in dist/index.mjs and inspect the process.kill call that receives SIGTSTP. Reproduce with command-code 0.30.2 on Windows 11 if possible, then verify that the terminal command no longer crashes when this signal is encountered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100