-
Notifications
You must be signed in to change notification settings - Fork 2
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 exits early with "yarn watch" actions #4
Comments
From what I can tell, it looks like the way
https://github.com/matthewmcgarvey/nox/blob/main/src/nox/process.cr#L18 |
Easiest repro is to start with one of the repos I listed, but reduce your Procfile.dev to the following entries:
From there, you can see that |
Looks like this is an issue with Process#wait's implementation in Crystal.
|
Finally: |
Last bit of info for a while -- I think that the issue is that the way yarn scripts work is to run a script that starts other scripts -- here's a running log of what launches when I run both overmind and lucky dev (repeats every second, so you can see the termination output here as well)
|
Even if I change my Procfile to what appears to be "running" compared to Overmind (based on ps output), everything still exits; hopefully this helps the next person to try to pick up on this thread. Overmind works with this Procfile.dev as well, so at this point I'm wondering about node's exit codes themselves. 🤔
|
Yep, I see that too. It makes sense that |
Looking into it now, I'm seeing the js task complete but the css task continue to run and watch for changes.
|
Realized after doing some digging in the code that Nox was its own shard, and not embedded in lucky_cli.
luckyframework/lucky_cli#752
@matthewmcgarvey LMK if there's anything else I can do to help debug this.
The text was updated successfully, but these errors were encountered: