-
Notifications
You must be signed in to change notification settings - Fork 41
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
Silently returns incorrect results sporadically (Ubuntu) #79
Comments
I found this happens when the table does not line up. Try I found adding |
I ran into the same issue. I use ps-node to check if a process is still running and if not restart it. Every now and then it returns an empty array without an error. At the end of a day, about 15 processes are running. I didn't find a workaround yet. |
I have seen this happen on macOS too. |
I've seen it on macOS too. I captured some output that causes the table parser to fail: You can see there are some misaligned columns causing the TIME and COMMAND fields to have the same titleBegin.
|
ps-node has an issue (neekey/ps#79) and appears to have been abandoned This checks that the project id returned from /flowforge/info endpoint is consitent with the expect id
I have been using ps-node in production for about a year. I have experienced some mystery issues very rarely but never investigated closely enough until today. Finally I realize that, rarely, ps-node is failing to parse the process list correctly and is therefor returning incorrect results.
I know that there is a note about "limitations" for multiple-bytes characters. Is it possible that there was some other process in the system that was using a multi-byte character? Sure, how would I know? The point is that users can't know this, so the "limitation" should be rephrased as, "ps-node is unreliable and sometimes it returns incorrect information". I think this needs to be put up front, at the very top of the readme.
To summarize: ps-node is not to be used anywhere that reliability is important.
I still appreciate the work done by the module writers... I understand that parsing the command-line output is problematic and maybe even impossible in this case. I just think that users should understand this...
For what it's worth, below is an exerpt of what ps-node returned to me in the problem case. I haven't been able to repro since then so I don't know what tickled it. Note that instead of the actual command, some incorreclty-parsed digits are returned:
The text was updated successfully, but these errors were encountered: