Matthew Lieder

Results 46 comments of Matthew Lieder

Makes sense! I get a different exception with 39.0.2-beta1: ``` # AutoConnectAsync() # AutoDetectAsync(True, False) # Dispose() Status: Disposing FtpClient object... Unhandled exception. System.ArgumentException: Required parameter is null or blank....

Now complaining about profile.Credentials being null: ``` # AutoConnectAsync() # AutoDetectAsync(True, False) # Dispose() Status: Disposing FtpClient object... Unhandled exception. System.ArgumentException: Required parameter is null. (Parameter 'profile.Credentials') at FluentFTP.FtpClient.LoadProfile(FtpProfile profile)...

Your file attachment doesn't appear to have uploaded fully?

Thanks! It got much further, however it appears that it's skipping calling ConnectAsync: ``` # AutoConnectAsync() # AutoDetectAsync(True, False) # UploadBytesAsync("/site/wwwroot/somefile.json", Overwrite, False) # FileExistsAsync("/site/wwwroot/somefile.json") # Dispose() Status: Disposing FtpClient...

Closer, but not quite yet: ``` # AutoConnectAsync() # AutoDetectAsync(True, False) # ConnectAsync() Status: Connecting to ***:21 # Dispose() Status: Disposing FtpClient object... Status: Disposing FtpSocketStream... Unhandled exception. System.TimeoutException: Timed...

We have a winner! ``` # AutoConnectAsync() # AutoDetectAsync(True, False) # ConnectAsync() Status: Connecting to ***:990 Status: FTPS Authentication Successful Status: Time to activate encryption: 0h 0m 0s. Total Seconds:...

That'll produce individual test reports, but won't produce a single combined test report (my impression of what this enhancement is for).

Just in the past week we've start running into this same issue on our Isolated app service plan in Azure, just with a slightly older host version (3.0.16.0). It only...

@brettsam How do I tell what version of the Functions Host my app is running on? It's not in my zip deploy archive, so it's part of the Azure environment...

`2021-02-16T15:57:55.9558916Z baa8f447-4f6e-4168-a18e-61b45acfba9`, East US. Last confirmed time this issue existed for us was ~1:00pm CST yesterday (when scaled up to four instances), though it's likely happened since too. If there's...