Without any information regarding what timeout(s) were set and were expected, the message "after 0 seconds" could be working-as-designed. All it's doing is saying how many seconds (rounded down) things took to fail, so if there's a 100ms timeout then that's all you'd ever see.
i.e. it's not the best error message ever for fast systems :-/
In general, it's best to configure the SSH connector to try multiple times and wait between attempts, and I'd guess that's not what's being done here (otherwise things wouldn't be able to fail so fast).
I've checked the PR and, yes, it looks like the code being changed may well be the source of this problem ... and that'll be discussed in the PR itself.