Repository navigation
Commit 30ae4ca
fix(cli): npm launcher no longer leaves a runtime running after a stop signal
The npm launcher forwarded SIGTERM/SIGHUP (and SIGINT under IPC) to the
runtime and then waited for it forever. A runtime that could not finish
shutting down kept the launcher alive until launchd SIGKILLed the launcher,
orphaning the runtime. After forwarding a stop signal, the launcher now
SIGKILLs the runtime if it has not exited within 5 s, matching the
`t3 service` launcher's terminateChild grace.
Fixes #30435
Co-Authored-By: Claude Opus 5.5 <[email protected]>1 parent e4345de commit 30ae4ca
1 file changed
Lines changed: 8 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
11 | 11 | | |
12 | 12 | | |
13 | 13 | | |
| 14 | + | |
| 15 | + | |
14 | 16 | | |
15 | 17 | | |
16 | 18 | | |
| |||
169 | 171 | | |
170 | 172 | | |
171 | 173 | | |
| 174 | + | |
172 | 175 | | |
173 | | - | |
| 176 | + | |
| 177 | + | |
| 178 | + | |
| 179 | + | |
| 180 | + | |
174 | 181 | | |
175 | 182 | | |
176 | 183 | | |
| |||
0 commit comments