Paul Meinhardt

I've started looking into this. My current insights: 1. The remote sends a "warning" with the message `"scp: /some/nonexistent/destination: No such file or directory\n"`: ```elixir {:data, channel, 0, } ```...

Sifting through the OpenSSH `scp` C sources, I understand the behavior as follows: Whenever the [remote (sink) sends a warning code `1`](https://github.com/openssh/openssh-portable/blob/4b22fd8ecefd059a66140be67f352eb6145a9d88/scp.c#L1289-L1307 ) in response to us (source) sending data…...

I initially thought this might be a quick thing and whipped up a PR: https://github.com/bitcrowd/sshkit.ex/pull/125 Now I'm not so sure how to deal with different versions of Elixir (e.g. our...

Any ideas on how to handle this are welcome. Should we just check formatting for the latest version in our build matrix?

The code shouldn't break, but `mix format --check-formatted` and thus CI might fail if the formatting preferences change between different Elixir versions I guess.

Hey @maltoe, it's been a while but the problem was that the formatting produced by `mix format` and expected by `mix format --check-formatted` differs between Elixir versions. However, since SSHKit...

Ah, I think now I get it. I feel a bit slow today. 😄 So what you're saying is you mean to apply "auto-formatting" in some automated way but not...

Hi there @d4rk5eed 👋 Sorry for the late reply, we are quite busy at the moment. Thanks a lot for using SSHKit.ex and reporting this issue 🤘 To make sure...

Hi @d4rk5eed, I am still not sure what we can do here at the moment since we cannot reproduce the issue reliably. If I had to guess, I'd say it...

Nice, thank you @seungjin 👍 Some quick, early feedback and thoughts: * If you could add tests, that'd be great 🙂 * I think that if we provide a timeout...