Closed mmrwoods closed 2 years ago
Thanks @mmrwoods for reporting the issue here. But it is better to fix forever bug instead of making changes in this repo in this case.
If changes are needed after fixing forever bug certainly i will consider it.
Thanks @arvind-agarwal, looks like it will get fixed on forever soon.
P.S. Sorry about delay following up, just a busy few days.
Forever version 4.0.3 changes the output from
forever --plain list
slightly which breaks the init script generated by forever-service because the regex to parse the output and determine the status of running services no longer works.With forever v4.0.2,
forever --plain list
generates output like this:With forever v4.0.3,
forever --plain list
generates output like this:That
undefined
afterdata:
breaks the init script created by forever-service as it relies on a regex matching whitespace afterdata:
to identify running services.I've reported this to the author of the relevant PR which introduced the change at https://github.com/foreversd/forever/pull/1128#issuecomment-1025476725 and it has been acknowledged as an issue, but that does not necessarily mean a fix is imminent.
In the meantime, I have pinned forever to version 4.0.2, but maybe the status regex in the init script generated by forever-service should be updated though to look for a sequence of characters not matching
[
rather than one or more spaces? (having said that, this is code I'm not really familiar with, it's just an issue I ran into earlier today, so I might be missing some obvious constraints here)