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.

Sign up for GitHub

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

Jump to bottom

Error reporting in asyncoperationstatus #93

Closed
jim-minter opened this issue Jan 20, 2020 · 1 comment
Closed

Error reporting in asyncoperationstatus #93

jim-minter opened this issue Jan 20, 2020 · 1 comment
Labels
priority-high High priority issue or pull request size-medium Size medium

Comments

@jim-minter
Copy link
Member

jim-minter commented Jan 20, 2020 •
edited
Loading

There is the provision to report operation errors back to the user via the operationsstatus API but we are currently hard coding any backend error to "internal server error".

There may be a few cases where we want to be clearer about what the backend error was - dns name collision is one example.

Inadequate quota is another.
@m1kola m1kola added enhancement New feature or request priority-low Low priority issue or pull request size-small Size small labels Jan 23, 2020
@jim-minter jim-minter added size-medium Size medium and removed enhancement New feature or request size-small Size small labels Jan 24, 2020
@mjudeikis mjudeikis mentioned this issue Jan 24, 2020
Closed
@jim-minter jim-minter added priority-high High priority issue or pull request and removed priority-low Low priority issue or pull request labels Jan 29, 2020
@jim-minter
Copy link
Member Author

->VSTS

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
priority-high High priority issue or pull request size-medium Size medium
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@m1kola @jim-minter