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
Combining --force and --silent #64
Comments
Yeah, that's a bug. It should work like you describe. PR welcome :) |
@issuehunt has funded $40.00 to this issue.
|
I looked into this. I wasn't able to reproduce it when cloning the repository. However, when installing it from Reason: Fix: Publish a new version with the current repository state to |
@sindresorhus Thoughts on the above? |
@ulken The bounty is yours if you submit a test that shows that it's already fixed. |
@sindresorhus has rewarded $36.00 to @ulken. See it on IssueHunt
|
We need to kill a node process that runs a server (e.g. on port 8000) as part of our deployment script.
Using "fkill :8000" doesn't terminate the process, so we need "fkill -f :8000"
Unfortunately, fkill is returning an error code when there is no process running on port 8000. So we added the silent switch "fkill -f -s :8000"
This works, but gives an error message when no process has been found, which should not be the case using -s.
IssueHunt Summary
ulken has been rewarded.
Backers (Total: $40.00)
Submitted pull Requests
Tips
IssueHunt has been backed by the following sponsors. Become a sponsor
The text was updated successfully, but these errors were encountered: