-
-
Notifications
You must be signed in to change notification settings - Fork 154
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
fix(watch): respawn process only after exit #244
Conversation
&& (!runProcess.killed && runProcess.exitCode === null) | ||
) { | ||
runProcess.kill(); | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you move this logic down right after the exit
handler is registered?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@privatenumber like that?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@privatenumber, could you take a look? Fixing this problem would improve developer experience quite a lot
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is a very useful feature, PTAL @privatenumber
Maintainer editing is disabled on this pull request, so I can't make changes or run tests. Closing in favor of #298 |
That code cause EADDRINUSE error in 50% of restarts in watch command if port binding going fast.
Aslo impossible to get around it with graceful shutdown logic.