John Eikenberry

Hey @sachinsingh2005, sorry for the delayed response. I'm not sure what else we can do with the information provided. There is no way for me to reproduce the issue and...

Sounds good. Please let me know what you find out.

client.ReadDir(path) was modeled after ioutils.ReadDir(path), not os/File.ReadDir(int). The sftp client library currently doesn't have an equivalent to os/File.ReadDir(int). The client library isn't built around the idea of the using the...

I don't think the File.ReadDir() is deprecated or anything, it is just a different way vs the ioutils list method. As for an implementation, I think it'd need to be...

Currently no. The protocol supports sending file attributes along with the Open packet, but the client implementation doesn't utilize that presently. I don't see anything preventing it from being added,...

sftp.NewClient takes a ssh.Client object as an argument and that ssh.Client object has the Wait() method. So if you keep a reference to the client you passed in, you already...

Thanks for the comment. We should probably add something in the docs for the NewClient function that mentions this. Another thing is that I noticed I was wrong in my...

I dug into the ssh.Session code a bit and it looks like when you close the sftp.Client() the correct close gets called on the session. The StdinPipe() returns a io.WriteCloser...

What I meant was that the ssh.Client doesn't have Wait, the ssh.Session does. But you pass NewClient() the ssh.Client and it creates the ssh.Session internally and doesn't store it directly....

@crazed Is your code that wraps the connection available anywhere? I was thinking about implementing something similar to see how it works and see if I could reduce it down...