overengineeringstudio / overengineeringstudio/effect-utils
Verify PTY wrapper exit code for interrupted TTY commands
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Follow-up from store GC interrupt work. The shared @overeng/tui-react runTuiMain path now maps interrupt-only Effect exits to process.exitCode 130 and has a unit test, and real PTY dry-run runs show visible ^C plus interrupted UI state. However, one bash/devenv PTY wrapper scenario still printed MR_EXIT:0 after a late interrupt. Need isolate whether this is pty/devenv/bash wrapper behavior, Bun/NodeRuntime signal semantics, or a remaining CLI boundary issue, and add a true process-level regression if needed. No private repository details included.
Posted on behalf of @schickling
| field | value |
|---|---|
agent_name |
✨ co2-quartz |
agent_session_id |
258a96de-66de-4452-be7a-369b85e7b244 |
agent_tool |
Codex CLI |
agent_tool_version |
0.130.0 |
agent_runtime |
Codex CLI 0.130.0 |
agent_model |
unknown |
worktree |
effect-utils/schickling/2026-05-26-mr-store-gc-bug |
machine |
mbp2025 |
tooling_profile |
dotfiles@4e6515b |
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 by reproducing the bash/devenv PTY wrapper scenario that reports MR_EXIT:0 after a late interrupt, then compare pty/devenv/bash behavior with Bun/NodeRuntime signal handling and the CLI boundary. Check the existing @overeng/tui-react runTuiMain unit test and real PTY dry-run behavior first. Done means identifying the failing boundary and adding a true process-level regression if the issue is in the project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- bash, typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100