Add basic examples and design goals to README #572
Comments
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
paulcsmith
added a commit
that referenced
this issue
Aug 23, 2018
djuber
pushed a commit
to djuber/lucky
that referenced
this issue
Aug 29, 2021
…le the signal and finish - rather than us immediately exiting and leaving it to log shutting down messages from the background (luckyframework#572) * lucky dev: When Ctrl+C is pressed, wait for the child process to handle the signal and finish - rather than us immediately exiting and leaving it to log shutting down messages from the background Resolves luckyframework#570. I've just used the approach I suggested there. I wasn't sure how/if to write a spec for this, so I haven't. Is that acceptable? To test it manually, I ran this from my app directory before and after the change to verify the behaviour: ```bash $ crystal run ~/Projects/lucky_cli/src/lucky.cr -- dev ``` * Update src/lucky_cli/process_runner.cr * oops. formatted Co-authored-by: Jeremy Woertink <jeremywoertink@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
No description provided.
The text was updated successfully, but these errors were encountered: