You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This suggests that monitor may not be used as originally intended, and it means that even successful restarts suffer from accumulated delays, keeping the child offline without reason.
Given the ressource limitations on this project, I would suggest a minor fix: after the fork (
currently, the following lines are dead code as
child
isnull
whenmonitor
is callednode-windows/lib/wrapper.js
Lines 120 to 125 in accfbd0
This suggests that
monitor
may not be used as originally intended, and it means that even successful restarts suffer from accumulated delays, keeping the child offline without reason.Given the ressource limitations on this project, I would suggest a minor fix: after the
fork
(node-windows/lib/wrapper.js
Line 162 in accfbd0
Also, please don't hide the child's exit code - it is sometimes the only available clue to what went wrong.
node-windows/lib/wrapper.js
Lines 165 to 166 in accfbd0
log.warn(argv.f+' stopped running with code: '+code.toString(16));
The text was updated successfully, but these errors were encountered: