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
feat(iot-dev): Fix file upload complete notification API #911
Conversation
completeFileUploadAsync does not behave asynchronously, so the name was a mistake. Deprecating that API and creating a new one without the Async suffix
/azp run |
Azure Pipelines successfully started running 4 pipeline(s). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this required for the .NET client as well?
Looks good. Should we patch the LTS ? |
No, because it is actually async in .NET This java function returns syncrhonously, so it should never have been post-fixed with "async" |
It isn't really a critical bug fix or a security fix, so I don't see a reason to |
When do we finally delete the deprecated functions? |
Never, probably |
completeFileUploadAsync does not behave asynchronously, so the name was a mistake. Deprecating that API and creating a new one without the Async suffix
#910