ddf2c014f1799731c07c4c7d9788f4f46e9237b6
withTimeout wrapped a blocking process.waitFor() that coroutine cancellation can't interrupt, so a hung process hung the stage until it exited on its own; and destroyForcibly() killed only the direct child, leaving sh -c grandchildren (the real npm/tsc) as orphans. Use process.waitFor(timeout, MILLISECONDS) for an on-the-clock deadline, and kill via toHandle().descendants() + the parent.
fix: workflow inference chain — surface llama-server errors, user-turn-last, bundle-relative prompts
Description
No description provided
Languages
Kotlin
88.4%
Go
11.4%
Python
0.2%