Skip to content
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

downloadBlobToWriterAt() does not execute Progress() function #16726

Closed
discentem opened this issue Jan 1, 2022 · 3 comments
Closed

downloadBlobToWriterAt() does not execute Progress() function #16726

discentem opened this issue Jan 1, 2022 · 3 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)

Comments

@discentem
Copy link
Contributor

discentem commented Jan 1, 2022

Bug Report

  • Import path: sdk/storage/azblob

but more specifically https://github.com/Azure/azure-sdk-for-go/blob/main/sdk/storage/azblob/highlevel.go#L284

  • SDK version: master

  • What happened?
    Setting Progress on HighLevelDownloadFromBlobOptions for DownloadBlobToFile does not work. The function does not appear to get executed.

I think this is because o.Progress(progress) is commented out. Why is it commented out? 😛 And I suspect this would cause Progress to get skipped for all DownloadBlob... functions.

Download: https://github.com/discentem/bk_azureblob/blob/c063613fcd0f5ce8305734239375e2cf0ace94ac/main.go#L105
Upload: https://github.com/discentem/bk_azureblob/blob/c063613fcd0f5ce8305734239375e2cf0ace94ac/main.go#L128

@ghost ghost added needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. customer-reported Issues that are reported by GitHub users external to the Azure organization. question The issue doesn't require a change to the product in order to be resolved. Most issues start as that labels Jan 1, 2022
@discentem discentem changed the title o.Progress(progress) is commented out in downloadBlobToWriterAt() downloadBlobToWriterAt() does not execute Progress() function Jan 1, 2022
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 3, 2022
@mohsha-msft
Copy link
Contributor

Hey @discentem ,

Thanks for pointing this out!
I've merged the changes in our development branch dev-azblob and we'll include these changes in the next release.
Can you please use dev-azblob branch in the meantime. i.e. go get github.com/Azure/azure-sdk-for-go/sdk/storage/azblob@dev-azblob

@RickWinter RickWinter added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) labels Jan 4, 2022
@ghost ghost added the needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team label Jan 4, 2022
@RickWinter RickWinter removed the azblob label Jan 4, 2022
@discentem
Copy link
Contributor Author

@mohsha-msft thanks so much for the merge! using dev-azblob branch works as expected. Not sure what the protocol here is but you can close the issue if it makes sense. Or will it stay open till the next release?

@mohsha-msft
Copy link
Contributor

Hey @discentem ,

Thanks for the confirmation. The issue will stay open till we make next release of the SDK.

@github-actions github-actions bot locked and limited conversation to collaborators Apr 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. customer-reported Issues that are reported by GitHub users external to the Azure organization. needs-team-attention Workflow: This issue needs attention from Azure service team or SDK team question The issue doesn't require a change to the product in order to be resolved. Most issues start as that Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

4 participants