-
Notifications
You must be signed in to change notification settings - Fork 944
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
Stopping by index terminates multiple processes (0.14.1) #699
Comments
This doesn't appear to be based on having the same name such as |
I suspect the bug is at https://github.com/foreverjs/forever/blob/509eaf24deaf1ea8515298d5fcf16708715e658c/lib/forever.js#L692 which is doing an
|
Related to #659? |
@kegsay I can confirm that your fix solves this problem for me. I consistently had all processes stopped when issuing a 'forever stop 0'. Modifying forever.findById() from 'return p.id == id;' to 'return p.id === id;' results in 'forever stop 0' killing only the process at index 0. Many thanks! |
We're also experiencing this issue. |
Fixed in 0.14.2 |
I have 0.14.2, and |
Sounds like this simply needs a failing test. Does anyone mind writing one? |
I can confirm that the latest NPM version does not contain the fix yet! Code of the affected file does not match the file in master branch which was updated with commit faa5d3a |
This issue still exists in v0.15.1 where #756 is fixed.
|
Expected: That the first process
[0]
would be killed byforever stop 0
.Actual: Both processes were terminated.
This may be related to: #481
Running node
v0.10.25
The text was updated successfully, but these errors were encountered: