Skip to content

[Release-1.4.0] Better Error communication in case of Long Running Operation #2182

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

Merged
merged 2 commits into from
Apr 30, 2016

Conversation

solankisamir
Copy link
Member

-Logging changes for better error communication to customer in case Long Running Operation fails
-Typo fixes in Message

- Logging changes for better error communication to customer in case
Long Running Operation fails
- Typo fixes in Message
@azurecla
Copy link

Hi @solankisamir, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!


It looks like you're working at Microsoft (sasolank). If you're full-time, we DON'T require a contribution license agreement.



If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@solankisamir
Copy link
Member Author

solankisamir commented Apr 29, 2016

@hovsepm hovsepm changed the title Better Error communication in case of Long Running Operation [Release-1.4.0] Better Error communication in case of Long Running Operation Apr 29, 2016
@markcowl markcowl merged commit e105e79 into Azure:release-1.4.0 Apr 30, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants