-
Notifications
You must be signed in to change notification settings - Fork 48
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
Nox process manager fails to keep certain processes running #752
Comments
ps output seems helpful here as well:
|
For context, horseshoe is a very vanilla lucky build, but the asset builder is using esbuild --watch |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm pretty sure this must relate to exit codes and how yarn wraps different types of ongoing watch processes + how Nox traps exit codes, but haven't dug in deeply yet.
https://github.com/robcole/lucky_nox_bug has a repo that can repro this (this is just a one-off creation from @grepsedawk's https://github.com/grepsedawk/horseshoe template starter).
Steps to replicate:
1 - Clone the repo.
2 - Run script/setup.
3 - Run
lucky dev
You'll note the following in the logs:
That alone isn't problematic, but any save events won't trigger a recompilation, as Nox seems to think the process has exited completely:
Compare this to overmind, and you'll note that overmind will continue to properly pick up on filesystem events and recompilation will be triggered in Lucky:
The text was updated successfully, but these errors were encountered: