🐛 BUG: Ctrl-C doesn’t stop 1.0.0-beta.21 dev server #3269
Comments
brycewray
changed the title
|
I will add that @Jutanium reports on Discord that he can't reproduce the issue on his Mac. He suggested that I try the other test environments on astro.new, which I did but, again, couldn't load 1.0.0-beta.21 to test them (each was still on 1.0.0-bet.20). |
|
I just upgraded one of my projects from .20 to .21 and am seeing this same behaviour with ctrl C not working. Downgrading back to .20 also fixed. Mine is Void Linux, but I can also test this on Mac and Arch Linux if helpful. |
|
@hayley on the Discord, @Jutanium advises his Mac has Apple Silicon. Mine is an Intel Mac. Am assuming your Linux box is using an x86 CPU. Can you test on an Intel Mac? Edit: disregard, saw your reply on the Discord (https://discord.com/channels/830184174198718474/830184175176122389/971100578908368957). Thanks! |
|
Being fixed in #3276. |
|
Thanks for reporting! |
@matthewp @FredKSchott Thank you folks for the quick fix incoming! |
|
Fixed by #3276, release will be coming in a few minutes. |
What version of
astroare you using?1.0.0-beta.21
Are you using an SSR adapter? If so, which one?
No
What package manager are you using?
npm
What operating system are you using?
macOS
Describe the Bug
When I run
astro dev, the terminal will not accept Ctrl-C as a stop command but, rather, just echoes^Cin the display. I tried it also withastro dev --experimental-static-build --experimental-integrationsand got the same result. (Could only suspend the job with Ctrl-Z, and then separately kill the suspended job.)Downgrading to 1.0.0-beta.20 solves the problem.
Note: I tried to create a minimal reproducible example but was unable to load 1.0.0-beta.21 successfully. The URL below is NOT usable, but simply something to allow me to submit the issue.
Link to Minimal Reproducible Example
https://stackblitz.com/github/kkvinmbxo
Participation
The text was updated successfully, but these errors were encountered: