search

Azure / azure-sdk-for-net

This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.
MIT License
5.47k stars 4.8k forks source link

Point to steps for resolving queue encoding issues with Functions #29216

Closed mattchenderson closed 4 months ago

mattchenderson commented 2 years ago

Library name

Microsoft.Azure.WebJobs.Extensions.Storage.Queues

Please describe the feature.

Microsoft.Azure.WebJobs.Extensions.Storage.Queues v4 (built on v11 storage SDK) assumes a base64 encoding as this was the behavior of the QueueClient at that time.

However, the current QueueClient defaults to no encoding, but the new v5 Functions extension for Queues still expects base64. This means that there are scenarios where there will be an encoding mismatch. We should catch that error, and when surfacing it to the user, we should point to documentation that describes the valid setups and what change they might need to make.

This is most commonly seen with a QueueTrigger responding to messages that have been written by a QueueClient, both at latest versions. The remediation then would be a host.json configuration flag on the Functions side to work with no encoding, or to change QueueClientOptions.MessageEncoding on the sender side.

jsquire commented 2 years ago

//cc: @seanmcc-msft

github-actions[bot] commented 4 months ago

Hi @mattchenderson, we deeply appreciate your input into this project. Regrettably, this issue has remained unresolved for over 2 years and inactive for 30 days, leading us to the decision to close it. We've implemented this policy to maintain the relevance of our issue queue and facilitate easier navigation for new contributors. If you still believe this topic requires attention, please feel free to create a new issue, referencing this one. Thank you for your understanding and ongoing support.