-
Notifications
You must be signed in to change notification settings - Fork 85
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
Not all exceptions will have a .read() method. #155
Conversation
Intended to resolve GitHub issue galaxyproject#116 (but the exception handling is still nasty)
Thanks for the fix @peterjc - I'll tweak it a little because it is causing the |
Not all exceptions will have a .read() method.
The second |
I'll finish up with #116 sometime today. tor. 30. apr. 2015 kl. 07.31 skrev John Chilton notifications@github.com:
|
It ALL bothers me. It's ghastly but I was hitting all manner of different, awful bioblend/TS exceptions and so I hacked together something functional. Then I started bumping up against the |
Good luck - there seems to be a lot of very different exceptions to think about here :( |
Crap - didn't see you were going to work on this and I tried to fix it for travis. What do we think about - https://github.com/galaxyproject/planemo/compare/master...jmchilton:exception_handling?expand=1. |
Assuming |
No worries @jmchilton, lgtm. :) Let's pretend I implemented it that nicely. |
Intended to partly address GitHub issue #116 (but the exception handling is still nasty). Before this change,
With this fix:
Clearly still room for improvement - this looks like JSON so we ought to be able to pull out the error message as the older error handling code tries to do.