You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On second thought - it would be a really bad idea to persist pids after the application crashes. You run the risk of cancelling the pid of some other process when restarting Cuttle. But in general I like this idea while the application is running to simplify the shutdown code.
We can inspect pids to be sure they are running lein with-profile +cuttle. And also it will keep us from have multiple Cuttle instances from trying to build the same project, though that's only really possible when running a release version alongside a dev version.
Activity
oakmac commentedon Jan 29, 2015
This is an excellent idea and should simplify the shutdown code.
On Thursday, January 29, 2015, Shaun LeBron notifications@github.com
wrote:
oakmac commentedon Jan 29, 2015
On second thought - it would be a really bad idea to persist pids after the application crashes. You run the risk of cancelling the pid of some other process when restarting Cuttle. But in general I like this idea while the application is running to simplify the shutdown code.
shaunlebron commentedon Jan 29, 2015
We can inspect pids to be sure they are running
lein with-profile +cuttle. And also it will keep us from have multiple Cuttle instances from trying to build the same project, though that's only really possible when running a release version alongside a dev version.