Python Durable functions were working fine in the previous version (osx-x64.3.0.263) . But in the new version (3.0.2750), we get the following error on our local:
[8/12/2020 2:10:11 PM] A host error has occurred during startup operation 'd4a00383-4f0e-4ed5-8a5a-b2b20836a565'.
[8/12/2020 2:10:11 PM] System.Private.CoreLib: Absolute path information is required. (Parameter 'assemblyPath').
Value cannot be null. (Parameter 'provider')
We can reproduce it on different machines (macOs Mojave) and switching back to older version of azure function core tools, it works fine.
I can confirm that this same problem occurs with node.js functions as well. How do I revert back to previous version.
I'm seeing the same issue with Java functions on macOS Catalina.
@neosource I was able to revert to the previous version by uninstalling the current version, and installing 3.0.2630 with npm.
npm i -g [email protected] --unsafe-perm true
Thanks for reporting. I can also repro on Mojave.
Likely related to #2107 #2108 @ankitkumarr Can you please look into? Thanks.
/cc @soninaren
I am also seeing this on MacOS running Visual Studio Code with
Azure Functions Core Tools (2.7.2748 Commit hash: 8c653424aeb6494704c80edb202dd357043ecdf8)
Function Runtime Version: 2.0.14192.0
[8/12/20 9:23:48 PM] Loading extension bundle from ~/.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.3.0
[8/12/20 9:23:48 PM] Loading startup extension 'AzureStorage'
[8/12/20 9:23:48 PM] A host error has occurred during startup operation '28dc9d28-7787-4774-af11-89098628255f'.
[8/12/20 9:23:48 PM] System.Private.CoreLib: Absolute path information is required.
[8/12/20 9:23:48 PM] Parameter name: assemblyPath.
Value cannot be null.
Parameter name: provider
Application is shutting down...
Not even sure why I'm on core tools 2.7 when other people are talking about 3.0... but I'm going to try to figure out the prior version (which strangely seems to still be in use by another function which is still working) and see if I can downgrade it.
Strangely, when I switch VSC to a different function, it works fine even though it reports the same version of the core tools:
Azure Functions Core Tools (2.7.2748 Commit hash: 8c653424aeb6494704c80edb202dd357043ecdf8)
Function Runtime Version: 2.0.14192.0
I suppose that suggests this might be a different issue, but as far as I'm aware, the only change I made was letting VSC install an update this morning. It is downloading the extensions to ~/.azure-functions-core-tools/Functions/ExtensionBundles/Microsoft.Azure.Functions.ExtensionBundle/1.3.0, which is not where they seem to be in the other function app, which doesn't even seem to mention it in the logs.
The issue would be in both V2 and V3 of Azure Functions Core Tools. We are working to release a fix for both of these versions.
@dxkaufman, The V2 core tools supports V2 Azure Functions Runtime and V3 supports the V3 Azure Functions Runtime. You can find more info here. You can check our project README.md to see how to install one over the other locally.
Thank you @ankitkumarr, that's very helpful. Do you have any idea when the fix will be ready?
Same issue with Python functions on Mac. Any way to downgrade with Homebrew?
Like @dxkaufman I let VSCode update the core tools and now I also have this problem on Catalina with a Python function. I see it with v2 and v3 if I use brew link to switch between them.
Installing the older version using NPM as amacmillanparks suggested seems to allow you to use func host start, but you have to uninstall the Homebrew version.
We'll have a new version published today. Thanks for your patience.
Use this command to downgrade on homebrew:
brew install https://raw.githubusercontent.com/Azure/homebrew-functions/e7ef5b54fb286e8b09f717e19558801f524c360e/Formula/[email protected]
And this should work for v2:
brew install https://raw.githubusercontent.com/Azure/homebrew-functions/fd0b8baefdac9755890940d984a1b4b29fd53d17/Formula/[email protected]
Thanks @anthonychu we just ran across this issue this AM, glad to see you guys are already on it!
@anthonychu Thank you for that! Now I can work on my debugging today!
Out of idle curiosity, are the build numbers auto-updated every time someone checks in a revision?
Thank you all for your patience! We have released the hotfixed versions of
These should be available to you now. Please update you core tools version using any of our supported package managers (brew, npm, apt, choco).
Closing this issue, but please let us know if you continue to see this issue and we can re-open. Thanks!
I'm still receiving this error in VS Code with the latest version installed (3.0.2798) with the "standard" node template:
A host error has occurred during startup operation 'e12c8350-a6d8-4599-898f-cdaf6d3f77d8'.
System.Net.Http: An error occurred while sending the request. System.Net.Security: Cannot determine the frame size or a corrupted frame was received.
Value cannot be null. (Parameter 'provider')
@ankitkumarr can you please look into this?
@ajtatum, would you mind opening a different issue please? Your error seems different than the one reported in this issue, and is likely unrelated to the problem discussed.
When you open the new issue, please provide more information like -- the OS you are running on, if downgrading the version helps, and the error output if you set an environment variable CLI_DEBUG=1 and then run the function.
Thanks!
Most helpful comment
I'm seeing the same issue with Java functions on macOS Catalina.
@neosource I was able to revert to the previous version by uninstalling the current version, and installing 3.0.2630 with npm.
npm i -g [email protected] --unsafe-perm true