System.NotSupportedException: Request 'ping' is not supported.

[anandgmenon]

I am from the Azure Logic apps team and we use the library in the SFTP connector there.
For one of the users (SFTP server used is in-house system developed using Golang) we are seeing the ListDirectory method intermittently fails with the below exception

System.NotSupportedException: Request 'ping' is not supported.
   at Renci.SshNet.Common.AsyncResult.EndInvoke()
   at Renci.SshNet.SftpClient.EndListDirectory(IAsyncResult asyncResult)
   at Microsoft.Azure.Workflows.ServiceProviders.Sftp.Clients.SftpClientWrapper.EndListDirectory(IAsyncResult asyncResult)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

Our code looks like this

var authenticationMethods = new List<AuthenticationMethod>();

authenticationMethods.Add(new PasswordAuthenticationMethod(
    username: key.Username,
    password: key.Password));

var sftpConnectionInfo = new ConnectionInfo(
    host: key.Host,
    username: key.Username,
    port: key.Port,
    authenticationMethods: authMethods.ToArray());

client.Connect();

var directoryContents = await Task.Factory
    .FromAsync(
        beginMethod: (asyncCallback, state) => client.BeginListDirectory(
            path: targetDirectory,
            asyncCallback: asyncCallback,
            state: state),
        endMethod: client.EndListDirectory,
        state: null)
   .ConfigureAwait(continueOnCapturedContext: false);

We saw a similar issue #638 and noticed the fix is merged. However we tried with the latest bits from develop branch and noticed the issue persists.

Please provide your inisights on the issue and let us know if there's a workaround or fix possible.

[Rob-Hague]

If I perform a regex search in the project for "Request.*is not supported", I do not get any results. Perhaps you can check you do have 70a0a08? What commit do you have as latest?

[anandgmenon]

When we tested we had 749a0e0 as the last commit, which included 70a0a08

[mus65]

I don't see how this could still happen with 749a0e0 . As Rob mentioned, the error message doesn't even exist in the code anymore. I assume you have some mistake in your build or deployment and are actually still running an older version.

[anandgmenon]

Oh maybe some issues on build from my end, but would it be possible to release a new version so that its easier for us to test?

[mus65]

Note that there is also a workaround for older version ,see #1218 (comment)

[anandgmenon]

@mus65 the workaround for the old version didn't work, but we tried the latest version and seems to be working. However we'll need a new release to fix it officially. Last time @Rob-Hague mentioned there would be release in May. Can we get a release soon?