Patrick Stadler

Please check this. https://github.com/pstadler/flightplan/issues/117#issuecomment-178592529 PRs are welcome, as I don't have much time to work on open source projects currently.

This is odd. Is this also happening when the `failsafe` option is disabled?

Unfortunately, I'm not able to reproduce this. Could you please replace `lib/transport/ssh.js` with the following file containing some more logging and re-run your test case -- that would be incredibly...

Expected output: ```bash x.x.x.x $ which bar x.x.x.x > bar not found x.x.x.x ● DEBUG: exit-start 1 x.x.x.x ● DEBUG: exit-end 1 x.x.x.x > x.x.x.x ● DEBUG: end-start 1 x.x.x.x...

Thank you, this is incredibly helpful. It really seems like there's a race condition where the exit event is not thrown, or simply too late.

I tried multiple workarounds. Before continuing, it would be great if you could replace `lib/transport/ssh.js` with the following code and run your tests again, as I'm still unable to reproduce...

Thanks for your contribution. Could you write tests for it? Check https://github.com/pstadler/flightplan/blob/master/test/test.flightplan.js

Do you want to continue here?

Pull requests are welcome.

This would be possible somehow. However, I'm currently pretty busy. Check out the docs at https://github.com/mscdex/ssh2 regarding connection hopping in case you want to dive in. Best, Patrick