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

[FEATURE REQ] Add an onDataFinalized Method to ProgressReceiver #18762

Closed
gapra-msft opened this issue Jan 22, 2021 · 3 comments
Closed

[FEATURE REQ] Add an onDataFinalized Method to ProgressReceiver #18762

gapra-msft opened this issue Jan 22, 2021 · 3 comments
Assignees
Labels
Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files)

Comments

@gapra-msft
Copy link
Member

There is a delay between when the progress receiver says the last chunk of data has been sent and the upload finally completes.

We could possibly add an onDataFinalized method to the progress receiver when we issue the final commit block list.

@ghost ghost added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 22, 2021
@gapra-msft gapra-msft added Client This issue points to a problem in the data-plane of the library. Storage Storage Service (Queues, Blobs, Files) labels Jan 22, 2021
@ghost ghost removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Jan 22, 2021
@gapra-msft
Copy link
Member Author

Issues reported here #18389 and here #18700

@gapra-msft
Copy link
Member Author

To make progress receiver information more clear we could add to the receiver only on the onComplete of the stageBlocks instead

azure-sdk pushed a commit to azure-sdk/azure-sdk-for-java that referenced this issue Apr 21, 2022
[synapse][mgmt] extract common definition for `CloudError` (Azure#18762)

* Update readme.python.md

* update

* fix
@kasobol-msft kasobol-msft self-assigned this Jun 22, 2022
Copy link

Hi @gapra-msft, we deeply appreciate your input into this project. Regrettably, this issue has remained inactive for over 2 years, 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.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Mar 18, 2024
@github-actions github-actions bot locked and limited conversation to collaborators Mar 18, 2024
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. Storage Storage Service (Queues, Blobs, Files)
Projects
None yet
Development

No branches or pull requests

2 participants