Closed thomasfrederikhoeck closed 1 year ago
Hi @gavin-aguiar . I can see @vrdmr assigned you to this. Have you been able to replicate?
@gavin-aguiar @vrdmr is this actively worked on? :-)
@thomasfrederikhoeck We are investigating on this will update you the findings soon.
@ramya894 sounds good!
@thomasfrederikhoeck We are able to reproduce the problem and working on the solution to fix it. Thanks.
Hi @thomasfrederikhoeck , apologies for the late response. We are looking into this error. In the mean time for mitigation, remove the type in the definition as you mentioned. Locally, you can invoke the warmup trigger by calling http://localhost:7071/admin/warmup. In Azure, the warmup trigger will be called only during scale out operations.
@gavin-aguiar Thank you. I have tried the work around and that works. However it still requires me to call the endpoint. Will the fix you have merged automatically call the warmup trigger when starting a local debug?
@thomasfrederikhoeck Hi Thomas, in local the warmup trigger wont be automatically called. its only invoked by runtime in scaling scenarios, i.e in dedicated or elastic premium plans.
Gotcha. Then I think it would be meanigfull to show the endpoint in the startup messeage. In the following it is very hard to see that you need to call http://localhost:7071/admin/warmup to run it.
Investigative information
Please provide the following:
Repro steps
Provide the steps required to reproduce the problem:
httpTrigger
and awarmupTrigger
following the official guide https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-warmup?tabs=in-process&pivots=programming-language-python:If I try and remove the type it is never run which can be seen as this Exception is never hit
Expected behavior
Provide a description of the expected behavior.
It should locally when I run it as according to the guide
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-warmup?tabs=in-process&pivots=programming-language-python
Actual behavior
Provide a description of the actual behavior observed.
Raises the error:
Known workarounds
Provide a description of any known workarounds.
Contents of the requirements.txt file:
Provide the requirements.txt file to help us find out module related issues.
Related information
Provide any related information