overengineeringstudio / overengineeringstudio/effect-utils
devenv shell commands produce empty output when run in background
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 82
- Forks
- 2
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 121
Description
Problem
Running devenv shell -- bash -c '<command>' in background produces 0-byte output files for extended periods (60+ seconds), even though the command eventually completes successfully.
Reproduction
- Run a command via
devenv shell -- bash -c 'echo hello'redirecting output to a file - Check the output file — it remains empty for a long time
- Eventually the command completes and output appears (or doesn't)
Impact
Makes it difficult to use devenv shell commands in automated/background contexts (e.g. CI, agent workflows) where you need to monitor output progress.
Filed by Claude on behalf of @schickling
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 devenv shell command entry point and reproduce the background invocation with redirected output. Trace how command output is spawned and flushed, then verify that output appears promptly while the command runs and that the existing reproduction completes successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100