You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fix: Kill button now works by finding actual command PID
The issue was that when using shell: true, execa returns the shell's PID,
not the actual command's PID (e.g., sleep). The shell often exits immediately
after spawning the command, making the stored PID invalid.
Fix:
1. Store subprocess reference as instance variable to enable subprocess.kill()
2. After spawning, use psTree to find child processes and update PID to the actual command
3. In abort(), try both subprocess.kill() and direct process.kill() on the updated PID
4. Add stream wrapper to handle TypeScript types (execa can return string or Uint8Array)
This seems to be broken since PR #3136 which switched from AbortController to manual process killing
but didn't account for the shell vs command PID difference.
0 commit comments