No HTTP triggers found #1774
Comments
|
Hi @JackH11, Thank you for submitting this ticket. Seems to be related to microsoft/vscode-azurefunctions#2529 |
|
I have the same issue, even when trying to use a default template Http Trigger example. |
|
Thanks @IlyaBelykh for reaching out. Could you please share logs if you have them available? |
My logs seem pretty much the same as the ones given: |
|
I also must specify that I am using the V2 programming model. When uploading the V1 programming model function, it works perfectly fine. |
|
As I was running into a similar issue. I found I missed a step from the documentation, which enables the HTTP triggers to be found. Not sure if related to this specific issue, but might help others coming here with similar. |
|
Hi Any Update on this I am still getting the same issue. I can run the azure function locally but when I try to deploy it I get the same logs. |
|
add AzureWebJobsFeatureFlags with a value of EnableWorkerIndexing |
|
I've the same error, even if I've added the Here the log:
|
|
Had the same issue, trying to deploy Node.js functions using v4. |
I solved my problem. The problem was that I was using some app settings variables in my code and I added them in the |
Yes, It helped also here. Thank you |
|
If you are using a version lower than node js version 18, try updating to version 18 before proceeding. |
|
It happened to me again, and it took me an entire day to figure out that some packages in devDependencies had to be moved to dependencies for the HTTP trigger to work. |
|
Debugging this type of error is exhausting and often does not lead to a solution. There is definitely a need for logging that also reports these anomalies clearly. |
|
I am having this issue now as well; debugging locally works and this is set: |
To fix the issue, go to your function app in Azure portal, click on configuration, in application settings add a new key"azureWebJobsFeatureFlags" with a value of "EnableWorkerIndexing", then redeploy, this fixed the issue for me |
|
why is it that every time i try to learn any Azure tool i hit roadblocks exactly like this where there is no information, almost nothing to go by when debugging, and the whole thing just feels incredibly opaque and difficult? Even for the most basic task? |
|
It's why now we're the beta testers of these solutions. The important thing is not releasing a quality product, but any product as soon as possibile.
I found an awful bug in application settings using Python. Custom setting must be at the beginning of the list of application settings. If one of that variables was between the default one, I got the no HTTP triggers found error.
…--
Luca Zavarella | Microsoft MVP in AI and Data Platform
________________________________
From: Ross Campbell ***@***.***>
Sent: Friday, April 14, 2023 1:33:04 PM
To: microsoft/Oryx ***@***.***>
Cc: Luca Zavarella ***@***.***>; Comment ***@***.***>
Subject: Re: [microsoft/Oryx] No HTTP triggers found (Issue #1774)
why is it that every time i try to learn any Azure tool i hit roadblocks exactly like this where there is no information, almost nothing to go by when debugging, and the whole thing just feels incredibly opaque and difficult? Even for the most basic task?
i have the same error. No HTTP triggers found even though I'm using Azure's own boilerplate and everything works in locally-hosted debug mode. sigh.
—
Reply to this email directly, view it on GitHub<#1774 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ABOSK5MYM6CDDQXNOSQ6LNDXBEYXBANCNFSM6AAAAAATPKE3ME>.
You are receiving this because you commented.Message ID: ***@***.***>
|
|
Hello all, sorry for the delay in responding to you all. Oryx is used to build the code, but is not related to the deployment of these to Azure Web Apps, Azure Functions, StaticWebApps, etc. It looks like the Oryx build was able to pass for all of the code shared, and everything below the line The VSCode Azure Fn repo would be a better place to get support for this issue: https://github.com/microsoft/vscode-azurefunctions |
|
I had the same problem: No HTTP triggers found. The problem for me is that a requirement was missing in the requirements.txt file. |
|
same |
|
I figured out the cause and found a solution in my case. Here's what I found in case you're having the same issue. You cannot deploy a workspace in a monorepo. At least in my case, as soon as I de-listed the workspace in the monorepo's packages property everything works fine. I think the deployment is getting confused by the nested package structure. |
|
In my case, the solution was what Luca described back in March, a mismatch between app settings variables in the local.settings.json file and variables in the Azure function App Settings configuration. I am using the Python SDK V2 |
|
I was having this exact issue using Python Programming Model V2. My function is using some environment variables declared in local.settings.json for my local deployment. As commented in this thread previously. You need to add ALL of these values to your functions applications settings, just as the documentation explicitly points out for Once the values were added, deployment worked correctly. |
|
Hi all, I run into the same "bug". I develop my function code with VS-Code in python. I used the v2 model and had an already working function with a HTTP-Trigger. As soon as I want to add an output binding for CosmosDB (by adding the cosmos_db_output decorator to my function) following the guides, I get the "No HTTP triggers found". I setup the connection string via app settings, as well as AzureWebJobsFeatureFlags. As I said, when I remove the decorator and use it as a simple HTTP Trigger it works. When I try to add the cosmosDB binding, my function will run locally and also push documents into my CosmosDB without trouble, but I cannot, for the sake of it, deploy the function with a CosmosDB trigger. I am on this for 2 days already and I don't know what to do and where to look anymore, does someone have an idea or any pointers? |
|
I had to return to model v1. Without logs is very difficult to catch the
error.
El mar, 16 de may de 2023, 7:48 a. m., David Schu ***@***.***>
escribió:
… Hi all,
I run into the same "bug". I develop my function code with VS-Code in
python. I used the v2 model and had an already working function with a
HTTP-Trigger. As soon as I want to add an output binding for CosmosDB (by
adding the cosmos_db_output decorator to my function) following the guides,
I get the "No HTTP triggers found". I setup the connection string via app
settings, as well as AzureWebJobsFeatureFlags. As I said, when I remove the
decorator and use it as a simple HTTP Trigger it works. When I try to add
the cosmosDB binding, my function will run locally and also push documents
into my CosmosDB without trouble, but I cannot, for the sake of it, deploy
the function with a CosmosDB trigger.
I am on this for 2 days already and I don't know what to do and where to
look anymore, does someone have an idea or any pointers?
—
Reply to this email directly, view it on GitHub
<#1774 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AENF6OBV3Q4U2FLNGSICD6DXGNZQDANCNFSM6AAAAAATPKE3ME>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Thanks very much. I created a new V1 Model Function from scratch, implemented a very basic cosmos interaction, made it work and then migrated the rest of my code into the V1 Model. It is now working. |
|
For those still experiencing this issue even after setting their That is, instead of writing your import azure.functions as func
from src.mypckg import foo
# ... other imports
app = func.FunctionApp()
@app.function_name('myfunction')
async def main(...)
...
Try with this: import azure.functions as func
app = func.FunctionApp()
@app.function_name('myfunction')
async def main(...)
# YOUR IMPORTS HERE <--
from src.mypckg import foo
# ... other imports
...My guess is that the Azure runtime tries to run the |
Yes. Also on this issue, none of the other things worked. Trying again here: |
|
I am also unable to deploy my JS v4 functions from VSCode because of this error. This makes Azure Functions unusable for me. |
|
The first version of @azure/functions V4 was one year ago, and today it doesn't work correctly... |
|
After trying all above recommondations I still did not succeded to get de Functions visible. But I got it working again! I did 2 things, but not sure which one did the trick... I added a Try Except statements around my import packages. Like so: When importing packages the function won't crash on error and will show the function triggers. But when running the Azure Function it will show a runtime error, hopefully with a message thats meaningfull. Secondly I added fixed versions to my requirements.txt. Like so: I noted that package azure-storage-file-datalake was just updated to a new version. (the next day there was already a .1 version which suggest there was a issue within the package) Sadly I couldn't reproduce the issue so I am not 100% sure what got the function working again. |
|
I just ran into this, turned out to be a mismatch on the python version between the Azure function settings and the "Use Python Version" step in my deployment pipeline. |
|
Dropping down to Python 3.10 (from 3.11) fixed the "No HTTP triggers found" for me |
|
So, I tried everything before and it did not work... async def list_files(q: Union[str, None] = None): #<------ This work
async def list_files(q: str | None = None): #<----- This does NOT work |
I did exactly this after trying everything of the above. And now it works! thank you for posting your solution. I specified the numpy version that I´m using in my virtual environment and that did the trick, however I´m not sure why that fixes the problem. |
|
I went back to my project, and suddenly all my functions on Azure is gone, its huge project, and this is day 5 trying to get the functions to be visible, they work locally, but not when deployed, I get no http triggers found. 19:02:41 booking-shopify-api: Starting deployment... How do we debug this? it worked before!! |
solved the issue for me as well. Pretty sure the try catch solved it. When excecuting now my http request I get an error that one of my libraries is not found. |
Can't trust Microsoft. Same bug for me. SImple setup: Using v4, and Py 3.11 |
|
Faced same problem. Putting try: [imports] except: pass, as suggested by mitchelmeijer worked. Thanks |
|
for those still facing the issue with azure functions giving "No HTTP triggers found". The template code generated by default for v2 model is missing a few essential lines. Replace the code with following. |
Sir, thank you so much! If any one is trying import some module into the function_app.py. Do exactly what is being shown above! |
|
Just adding to this knowledge base of whatever could've actually caused "No HTTP triggers found", since this thread shows up top of the google search. My issue was because of having too many constants outside the |
|
For me this was caused by two things, relative imports being funky and initializing classes outside of Azure functions. Code base was Python. The lack of error logs was frustrating. 😭😭 |
|
For me fix was to set Node version to 20 (was 18). Error message are really useless. |
|
I was struggling with this for a few hours. Turns out that I needed to configure the Azure Function to be 64-bit instead of the default 32-bit. I had to revert to NodeJs V3, which gave me the exception that I needed. |
|
Keeping this issue open to help others landing here. Even though we're covering a wide array of related issues in one. |
This solved it. But I believed the solution is because of the pkg version. I updated the requirement.txt file of mine to the same version of my running on my local machine. I didn't put the try and except and it magically working. So it looks like some of the updated pkg is preventing the importing process. |
Thank you so much! I also encountered the same problem because I didn't include a package in requirements.txt. |
Thanks a lot. You are a life saver. Its unfortunate that psycopg2 still doesn't work. |
|
Same issue here. For me the solution was to add to azure function all the app settings and then deploy. |
THIS IS SUPER SMART WIth this trick the functions were loaded, then I was able to see them, but I wasnt able to execute them because the api key page was not loading (internal server error). So I changed my functions to ANONYMOUS and tried again, and indeed I was missing a setting in key vault which is loaded in the imports! Microsoft! please fix t his with logging at least! this is very difficult to debug. |
and others
Bug Report
At what date and time did you most recently experience the problem?
Experiencing this problem on 1/2/2023
Where did you experience the problem? E.g. Azure Web Apps, Azure Functions, Azure Container Registry, or offline use.
Experienced the problem while trying to deploy an HTTP request-triggered function to azure.
If your repo is publicly available please share its URL:
I used VSCode Azure Functions extension to create a quick-start http request. I also created a python virtual environment to run locally.
What happened?
I followed this walkthrough: https://learn.microsoft.com/en-us/azure/azure-functions/create-first-function-vs-code-python?pivots=python-mode-decorators#publish-the-project-to-azure, with the only change I made found here: http_auth_level parameters causes Type Error MicrosoftDocs/azure-docs#103178.
The function and trigger work when testing locally through azurite. Once I got to deploying the function from vscode, I received the output: "No HTTP triggers found". The function and trigger work when testing locally through azurite.
After the upload has been attempted, I can however see the project files that I uploaded under the "files" dropdown when viewing azure subscription through vscode.
What did you expect or want to happen?
I expected the function to deploy
How can we reproduce it?
Follow the walkthrough and make the replacement.
Do you have log output? Please include between the backticks:
The text was updated successfully, but these errors were encountered: