Handle interrupted error from mio

[rschoon]

mio 0.7 was changed to no longer automatically retry on system call interruption, so we now must do it ourselves. For example, the process receiving SIGINT could cause notify to panic, if the signal handler had been changed from default:

thread '<unnamed>' panicked at 'poll failed: Os { code: 4, kind: Interrupted, message: "Interrupted system call" }', /home/rschoon/.cargo/registry/src/github.com-1ecc6299db9ec823/notify-5.0.0-pre.5/src/inotify.rs:134:47

This change basically just ignores it (since we'll retry when we go through the loop again).

[0xpr03]

Could we test this somehow in CI ?

[rschoon]

Probably, although getting it right seems like it might be a bit complicated. Doing it as an integration test and sending a signal to its own pid would probably be sufficient to exercise the problem, but verifying things went according to plan might be harder.

I might take a look if I have time.

[JohnTitor]

LGTM, I think it's worth mentioning this in the changelog, could you add an entry?

@0xpr03 Feel free to merge once it's done :)

[0xpr03]

Thanks for tackling this !