Getting only 404 after runtime update to 2.0.11776-alpha

[forki]

The beta runtime was updated to 11776 and now I only get 404 if I try to run my functions in the portal. All functions used to work and now the are broken.

Investigative information

Please provide the following:

• Function App version (1.0 or 2.0-beta): beta
• Function App name: ecarbeta
• Function name: e.g. CheckTransactions
• Region: Europe West

Repro steps

go to portal an run function CheckTransactions
--> 404

Expected behavior

functions executes and returns without error

Actual behavior

getting 404 and function is not executed at all

Known workarounds

None. It's completely broken for me

/cc @fabiocav

[forki]

Created support request: 118052218231390

[forki]

I deleted that functionapp and created a new one called "ecarjobs". but same thing. only 404

[forki]

From logs:
Warning: Only got partial types from assembly: CheckTransactions, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Exception message: System.Reflection.ReflectionTypeLoadException: Unable to load one or more of the requested types. Retrieve the LoaderExceptions property for more information.
at System.Reflection.RuntimeModule.GetTypes(RuntimeModule module)
at System.Reflection.RuntimeModule.GetTypes()
at System.Reflection.Assembly.GetTypes()
at Microsoft.Azure.WebJobs.Host.Indexers.DefaultTypeLocator.FindTypes(Assembly assembly, IEnumerable`1 extensionAssemblies) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Indexers\DefaultTypeLocator.cs:line 120

[cyky]

Version 11776 seems to have some breaking changes. See details: Azure Functions Runtime 2.0 Preview Breaking Change Notice

You can rollback to earlier version and that might fix the problem for now.

[forki]

@cyky tbh I actually want to have the new version resolution changes. I'd appreciate someone from the team or support takes a deeper look. At least the error reporting needs to be improve here.

[cyky]

@forki I understand. Just wanted to let you know that there is "workaround" as I stumbled here due to a similar problem.

[pragnagopa]

Added this to breaking changes investigations issue.

[fabiocav]

@forki we'll be looking at the details to see what is going on with your app. Support might be unable to help since this is with the preview bits.

[forki]

Thanks @fabiocav.

[paulbatum]

@fabiocav I think the underlying assembly load failure is being hidden because that exception handler does not inspect the LoaderExceptions

Its also interesting that this code path has now become a hotspot for assembly load failures. Do you know why this is the case? All sorts of assembly load failures were possible before the loadcontext changes but they never manifested in this code path as best as I can recall...

[fabiocav]

@paulbatum yes, that code has to be enhanced to properly report the error.

We've seen failures with that code path before the changes (we looked at a few last week), but it all depends on when those assemblies are requested. In the functions scenarios, we'd typically see that early as we probe for extensions.

[paulbatum]

Last week doesn't count - LoadContext changes were already in at that point! I'm talking about the many months previous.