fix: correctly deserialize blob length #252
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Python library incorrectly decodes the length of a blob when the blob is triggered. this issue persists since ext bundle ver 2-3. Not a change caused by blob sdk https://github.com/search?q=repo%3AAzure%2Fazure-sdk-for-net%20blobproperties&type=code
or dotnet blob extension https://github.com/Azure/azure-functions-dotnet-worker/tree/main/extensions/Worker.Extensions.Storage.Blobs/src
or function host.
reference to node function: Azure/azure-functions-nodejs-worker#729 customers starting accessing blob length by "contentlength" attribute since 2017.