Commit 27b066f
committed
fix(runserver): don't capture watch subprocess stdout
Both ProcessManager and MultiWatchProcessManager spawned the Tailwind
CLI watch subprocess with `stdout=PIPE, stderr=STDOUT` but never read
from the pipe — the monitor loop only polls process state. Once the OS
pipe buffer (~64 KB on Linux) fills up, the watcher blocks on its next
write and silently stops rebuilding, which is exactly the symptom you'd
never suspect in a long dev session.
Drop the stdout/stderr overrides (and the now-unnecessary bufsize=1) so
the watch subprocess inherits the parent streams. The watch output now
flows straight to the terminal — a UX improvement on top of the
deadlock fix, because the user can finally see rebuild progress during
`tailwind runserver`.1 parent 3587802 commit 27b066f
1 file changed
Lines changed: 7 additions & 7 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
1043 | 1043 | | |
1044 | 1044 | | |
1045 | 1045 | | |
1046 | | - | |
| 1046 | + | |
| 1047 | + | |
| 1048 | + | |
| 1049 | + | |
1047 | 1050 | | |
1048 | 1051 | | |
1049 | 1052 | | |
1050 | | - | |
1051 | | - | |
1052 | 1053 | | |
1053 | | - | |
1054 | 1054 | | |
1055 | 1055 | | |
1056 | 1056 | | |
| |||
1141 | 1141 | | |
1142 | 1142 | | |
1143 | 1143 | | |
| 1144 | + | |
| 1145 | + | |
| 1146 | + | |
1144 | 1147 | | |
1145 | 1148 | | |
1146 | 1149 | | |
1147 | | - | |
1148 | | - | |
1149 | 1150 | | |
1150 | | - | |
1151 | 1151 | | |
1152 | 1152 | | |
1153 | 1153 | | |
| |||
0 commit comments