Open ZirconCode opened 1 year ago
To try some random things which could be the cause, I rolled back azure extension version to 1.11 and get this error:
3:34:11 PM debugApp123: Deployment Failed. deployer = ms-azuretools-vscode deploymentPath = Functions App ZipDeploy. Extract zip. Remote build.
3:34:25 PM debugApp123: Deployment failed.
Also with no further explanation.
Checking the .zip files in the webjobstorage /data/SitePackages shows that the function files are present.
Sometimes I also get this error:
4:00:49 PM: Error: The operation was aborted.
Also with no further explanation.
Sorry for the inconvenience. The fix for this issue is merged and will be released soon.
Actually the bug Alex linked is just for Node.js, not Python. @ZirconCode I would recommend you file an issue on the Functions team focused on Python here: https://github.com/Azure/azure-functions-python-worker/issues
Thank you, appreciate the response, after some more exploration, I made a mother of all bug reports here: https://github.com/Azure/azure-functions-python-worker/issues/1306
I'm facing this same problem right now. Tried all hints posted here, on microsoft forum and stackoverflow. Sometimes I also got mentioned 4:00:49 PM: Error: The operation was aborted.
error without any explanations.
Any ideas how to fix that?
Any ideas, is it a problem with the local settings, with the code, or with the function app I'm trying to deploy to?
@karoldziubak use https://github.com/microsoft/vscode-azurefunctions/issues/4176 for tracking the "Error: The operation was aborted." issue.
Relevant threads: https://github.com/microsoft/vscode-azurefunctions/issues/2529 https://github.com/microsoft/Oryx/issues/1774
I create a default HTTP trigger function app. I can run it locally. When I try to deploy, it fails silently with:
Details: Python, Runtime v4, Linux premium plan Manjaro linux, vscode 1.81.1, azure extension 1.12.3
Things I have tried from relevant thread (1):
AzureWebJobsFeatureFlags:EnableWorkerIndexing
.I don't even know where to go from here, I sat in a support call for 2 hours and we couldn't solve this. There are no errors, anywhere.