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
Quitting the dev process does not actually stop the server #350
Comments
Hi @kentcdodds, thanks to the report. I'm investigating what's happening and I think that is something related to |
@BoostIO funded this issue with $40. See it on IssueHunt |
@pedronauck has started working. See it on IssueHunt |
@pedronauck has rewarded. See it on IssueHunt |
Fixed, will be release in the next version! |
Thank you! |
By the way, I've been using docz a lot lately and I really love it. Thank you for your work here! |
Thanks @kentcdodds, I was a little bit distant from docz in the last months because some personal issues, but now I came back and trying to work more frequently here again. If you have any feedback or bug report, please, talk with me dude 🙏 |
Bug Report
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
I'm not 100% how to reproduce this reliably. You could try starting docz and before it finishes starting, try to stop it (⌃+c). It doesn't stop and continues to try to compile.
I'm fairly certain that this also happens when it's been running. Maybe only when it's recompiling.
In order to allow us to quickly reproduce you issue please include a link to a reproduction repository.
Sorry, closed source :-(
Expected behavior
A clear and concise description of what you expected to happen..
I expect quitting the process to close all spawned subprocesses.
Environment
The text was updated successfully, but these errors were encountered: