You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on the GitHub issue discussions Azure/azure-functions-dotnet-worker#2682, it appears this is a known bug related to HttpResponseData, and the recommended workaround is to use the [HttpResult] attribute.
May I know if you update the sample code to incorporate the [HttpResult] attribute as well? This would help prevent confusion for others encountering the same issue.
The text was updated successfully, but these errors were encountered:
The sample should be modified into something similar to this sample using ASP.NET Core Integration (note that the types are ASP.NET Core types, not HttpResponseData).
Another option, if you choose to keep using the type HttpResponseData, is to opt out of ASP.NET Core Integration by changing your configuration as described in these docs.
Hi team,
I’m currently using the HTTP trigger with Kafka output binding, following the sample code found here: https://github.com/Azure/azure-functions-kafka-extension/blob/dev/samples/dotnet-isolated/confluent/KafkaOutput.cs. The function will succeed for one-time execution, but if we trigger it multiple times, it will failed with the exception following:
Based on the GitHub issue discussions Azure/azure-functions-dotnet-worker#2682, it appears this is a known bug related to HttpResponseData, and the recommended workaround is to use the [HttpResult] attribute.
May I know if you update the sample code to incorporate the [HttpResult] attribute as well? This would help prevent confusion for others encountering the same issue.
The text was updated successfully, but these errors were encountered: