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

More consistent handling of exceptions in backend #230

Open
arielge opened this issue Sep 12, 2022 · 0 comments
Open

More consistent handling of exceptions in backend #230

arielge opened this issue Sep 12, 2022 · 0 comments

Comments

@arielge
Copy link
Collaborator

arielge commented Sep 12, 2022

There are currently some inconsistencies with how exceptions are logged and handled in the backend.

We should aim that:
A. Every exception that is explicitly raised within the backend modules should be caught upstream (usually by the app or orchestrator). For instance we do not currently catch exceptions raised by orchestrator_api.delete_workspace()
B. Each such raised exception should have an informative message, and this message should be logged where the exception is caught.

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

No branches or pull requests

1 participant