-
Notifications
You must be signed in to change notification settings - Fork 188
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
NullReferenceException
in FunctionMetadataProviderGenerator
after upgrading Microsoft.Azure.Functions.Worker.Sdk
to 1.17.3
#2588
Comments
NullReferenceException
in FunctionMetadataProviderGenerator
after upgrading Microsoft.Azure.Functions.Worker.Sdk
to 1.17.3
We are facing the same issue and almost the same scenario, except we don't use durable entities, but we use orchestrators and HTTP-triggered functions. |
@kshyju thanks for your swift action and response. I’d be happy to test and validate it if there is a pre-release of the package. |
Same here - I'm just using HTTP triggered functions ... |
Used the repro from @roycornelissen and was able to resolve it with the latest fixes that @kshyju mentioned - we've released SDK |
Awesome, |
Thanks for confirming @roycornelissen. |
Description
After upgrading
Microsoft.Azure.Functions.Worker.Sdk
to1.17.3
this morning, our FunctionApp gives a warning:Since we turned on
WarningsAsErrors
it started failing our builds which is pretty annoying. Our Function app has durable entities, orchestrations and httptriggered functions.When building with diagnostic level verbosity, there is a little bit more detail:
Steps to reproduce
dotnet-isolated
If you downgrade
Microsoft.Azure.Functions.Worker.Sdk
to1.17.2
, the warning disappears.The text was updated successfully, but these errors were encountered: