-
Notifications
You must be signed in to change notification settings - Fork 50
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Functions not showing after deployment #599
Comments
Hi @krystofurr please take a look at these troubleshooting steps: https://learn.microsoft.com/en-us/azure/azure-functions/functions-node-troubleshoot?pivots=nodejs-model-v4 If the troubleshooting doc doesn't help, I have a few questions. Does the custom logic only have problems in Azure or does it work locally? It would be helpful to have some of your logs. If the problem reproduces locally, that would be the output of |
Thanks @ejizba for the response! It only has deployment problems in Azure. Seems to work fine locally when executing the client http trigger that initiates the orchestrator. I reviewed the links that you provided and here is some more insight into things. As I mentioned above I have some other Azure dependencies... "@azure/identity": "^4.0.1", So if I comment out anything that utilizes these dependencies in the project, it seems to fail finding the runtime and then switches to test mode. See the logs below when it fails to find any functions from the KUDU console...
and logs when I uncomment lines that use those dependencies and they deploy. It finds the functions....
|
Okay this sounds like a known issue that was fixed a while ago. Check your package-lock.json file for the "require-in-the-middle" package and make sure it's at least v7.0.0. If not, update your dependencies until it is. Usually people don't rely on "require-in-the-middle" directly, so it can be a bit of a pain to figure out where the dependency is coming from. Our original reports of this issue (see here) were typically for people using the "applicationinsights" package, but there could be other packages depending on it, too. |
I can also duplicate the issue outside of my own project by using a new generated durable function project through VS Code. Steps...
Add the following dependency to your project "@azure/storage-blob-changefeed": "^12.0.0-preview.4" Try to instantiate a change feed client in the activity ( It won't actually get a client without credentials, but it just being there is enough to reproduce the issue )
Deploy to Azure via pipeline. Used AzureFunctionApp@2 as 'runFromPackage' or 'zipDeploy' Deploy is successful and no functions show in Azure |
I don't have this "require-in-the-middle" package in my package-lock.json. In my project or the generated one. |
It's really weird that this doesn't repro locally. Can you share your app name so I can look at logs from our side? Here are steps to share it privately: https://github.com/Azure/azure-functions-host/wiki/Sharing-Your-Function-App-name-privately |
Unfortunately I can't share the app name. You can generate a blank application , go through the steps and try deploying it. That should provide the logs you need ? |
I tried your steps except deploying through VS Code and it worked just fine. This kind of error should be reproducible locally, so the fact that you can't do that makes me think it's a problem with your Azure Pipeline or the app itself in Azure |
I would double check to make sure you're committing your package-lock.json file to git (or yarn.lock if you're using yarn, etc.). These files should not be in your gitignore. Also in your pipeline, make sure you run |
Thanks for your help on this. Much appreciated. |
Hi there,
I started working with durable functions for a project at work and I've ran into something that I'm having difficulty troubleshooting. It seems that my project builds and executes fine locally. It also has no issue deploying to Azure it seems. But depending on whether I comment out some of the source code in some of my custom modules that are imported into activity functions...the functions in Azure show up / don't show up. I'm at a loss as to what is causing it. Obviously it seems to me that it's my custom logic but it builds and run fine locally as I mentioned.
Durable Functions Version: 4
I have 1 orchestrator, 1 http trigger client and 1 activity. Inside of the activity function I have a class that imports azure dependencies. Some of which are these:
"@azure/identity": "^4.0.1",
"@azure/storage-blob": "^12.17.0",
"@azure/storage-blob-changefeed": "^12.0.0-preview.4",
"@azure/storage-queue": "^12.16.0"
I've found if i comment out all of the logic in the class and just leave it as a skeleton basically, it deploys and shows the functions in Azure. Otherwise nothing shows. Files do get deployed because I've verified that the changes are in place. For deployment I'm using the following:
inputs:
connectedServiceNameARM: ${{ parameters.subscription }}
appType: "functionAppLinux"
appName: "my-durable_function_app-${{ parameters.env }}"
package: "$(Pipeline.Workspace)/drop/$(Build.BuildId).zip"
runtimeStack: 'NODE|20'
deploymentMethod: 'runFromPackage'
Is there anywhere in Azure Portal I can see if it's successfully recognized the durable function project and will post the functions under the 'Overview / Function Tab' in Azure ? It's a very strange issue
The text was updated successfully, but these errors were encountered: