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

Better error handling #25

Open
LourensVeen opened this issue Mar 21, 2017 · 2 comments
Open

Better error handling #25

LourensVeen opened this issue Mar 21, 2017 · 2 comments
Milestone

Comments

@LourensVeen
Copy link
Member

Goal: no exceptions come out no matter what you put in. Except the ones produced by cwltool in the output, those are not my responsibility.

@LourensVeen
Copy link
Member Author

LourensVeen commented Jun 28, 2017

  • Recover database after a crash
  • Reconnect to compute resource if connection is lost
  • Inspect source and think about what could go wrong
  • Make fuzz test

@LourensVeen
Copy link
Member Author

This should be quite good now, although I'd still like to do the above inspection and fuzz test just because I'm a perfectionist. So I'm going to leave this open, but it should be considered mostly fixed.

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