[Unexpected timeouts observed against local Azure Function cold-starts]

Summary: Report by @toddmeinershagen in #517 of TimeoutPolicy causing hangs when used with HttpClientFactory

Expected behavior: TimeoutPolicy with HttpClientFactory does not cause hangs when used with HttpClientFactory

Reported behaviour: TimeoutPolicy with HttpClientFactory causes hangs when used with HttpClientFactory

Steps / Code to reproduce the problem: not supplied.

[toddmeinershagen]

@reisenberger - I appreciate the dialog and ideas. I did try your suggestion of running the Azure function in a separate instance of Visual Studio and got the same results. However, when I published the function to the cloud and ran the client locally, it ran fine.

My guess is that there is some kind of optimization going on when running locally. The interesting thing is that the call never makes it to the function. So, whatever mechanics go on to handle the webhooks triggering do not work well in that scenario.

[reisenberger]

@toddmeinershagen Haven’t time to join you digging deeper at mo into the local Azure Function cold-start issues, unfortunately (time must go to other Polly issues), but interested what you find if you want to report back later. Thoughts were that you might see if the same issue reproduces when the Azure function is run out of (say) a different Visual Studio instance; or indeed simply run up on Azure rather than locally.