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
This line appears to be the culprit — there's a & (which backgrounds a process) where I suspect we want a &&. But it's a little hard to tell, perhaps it's intentional that it's trying to run a couple processes in parallel.
I don't see this issue occurring on my machine. Sending ctrl + c to interrupt a running ./serve causes the local site to stop responding when using ./serve or ./serve-fast and the PIDs associated with the running job/task disappear when doing a process list with ps -a.
I'm not sure what the difference could be but some here's some info about my local setup:
I tried a few different things to see if it changed the behavior I see:
I updated the ./serve script to run in a bash shell by changing #!/bin/sh at the top of the script to #!/bin/bash. Running this script in Kitty and in the default terminal application made no difference.
I tried running the ./serve script in the default terminal application and that made no difference.
I ran chsh -s /bin/bash to temporarily switch over to a bash shell and then running an unmodified ./serve script resulted in no changes, the process stops as expected when sent an interrupt.
Expected Behavior
When I run
./serve
and signal an interrupt (ctrl+C
), theserve
command should stop running and the site should stop working in the browser.Actual Behavior
When I run
./serve
and signal an interrupt (ctrl+C
),serve
continues running in the background and the local site continues to work.Steps to reproduce the behavior
./serve
ctrl+C
to interruptThis issue is done when
serve
shuts down when given an interrupt signal (ctrl+C
)The text was updated successfully, but these errors were encountered: