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 rates: Differentiate unexpected error/bug Vs expected error/user error #1528

Closed
ravipal opened this issue Jan 7, 2020 · 0 comments
Closed

Error rates: Differentiate unexpected error/bug Vs expected error/user error #1528

ravipal opened this issue Jan 7, 2020 · 0 comments
Assignees
@ravipal
Labels
P1
Milestone
0.10.0

Comments

@ravipal
Copy link
Contributor

ravipal commented Jan 7, 2020 •
edited

In general, any error thrown during command execution is reported as error and 'Report an issue' button is offered to user. But some of the errors are expected like user tries to delete an image that is in use or try to start/stop container but no container matches the required state exists and so on.
We need to a better way to categorize the error and offer 'Report an issue' button only on unknown/unexpected error.
@dbreshears dbreshears added this to the 0.10.0 milestone Jan 10, 2020
@dbreshears dbreshears added the P1 label Jan 10, 2020
This was referenced Jan 17, 2020
Merged
Merged
Merged
@ravipal ravipal closed this as completed Jan 21, 2020
@bwateratmsft bwateratmsft changed the title Differentiate unexpected error/bug Vs expected error/user error Error rates: Differentiate unexpected error/bug Vs expected error/user error Feb 10, 2020
@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@ravipal ravipal

Labels
P1
Projects
None yet
Milestone
0.10.0
Development

No branches or pull requests
2 participants
@ravipal @dbreshears