Alex Chaffee
Alex Chaffee
hmmm... good detective work. Will require more investigation...
Off the top of my head, no. There might be a way to patch it in if you can get the debugger to create/delete a little file that a patched...
I think this is a vote for a `--port` option, where rerun will announce that some process is now listening on that port. On its own rerun can't tell if...
this is sort of working now... i've now got a minimum 1 second delay between restarts; see https://github.com/alexch/rerun/blob/master/lib/rerun/watcher.rb#L60
That sounds like a cool feature. You're saying that when rerun re-launhes your program, it would send the list of modified/deleted/added files as parameters to the new run? That doesn't...
Sorry, I haven't worked on this issue yet... What version of foreman are you using? I would think `--signal KILL` would do it -- or even the normal `TERM` --...
Here's the relevant code: https://github.com/alexch/rerun/blob/master/lib/rerun/runner.rb#L218-L241 It looks like foreman is responding to SIGINT by sending SIGKILL to all its children. But it takes longer than 2 seconds for the children...
You've found a logical flaw in the config options. Basically, when an 'include' conflicts with an 'ignore', which takes priority?