-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Receives SIGTERM during "DDoS" #821
Labels
Comments
This issue has been inactive for 180 days |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environment Versions
$ node --version
v16.3.0$ http-server --version
v14.1.0Steps to reproduce
node demo/app.js
(you can run
npx -y kill-port 3000
to forcefully kill the http-server)Expected result
I expect http-server not to receive SIGTERM signal. I'm pretty sure that it's sending it to itself somehow?
Actual result
See in repro steps
Other information
My use-case is running cypress tests using http-server, and when I disabled cache using
-c-1
- it started to fail midway. When I run tests individually - they pass, but when I run them all sequentially - the server gets sigterm signal.I'll probably just ignore it because despite the server getting this signal, it still continues to work just fine.
This is kinda a problem when I do want to kill it tho, once all tests are done. Because
tree-kill
npm module that I use normally to kill http-server, doesn't work in this scenario.The text was updated successfully, but these errors were encountered: