-
Notifications
You must be signed in to change notification settings - Fork 445
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
Fail eagerly to wait for the idle status if we have reached a "final" status #81
Conversation
|
@@ -0,0 +1,3 @@ | |||
class LivyUnexpectedError(Exception): | |||
"""An exception that will be shown if some unexpected error happens on the Livy side.""" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we rename to LivyUnexpectedFinalStatusErrors? This seems too broad.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My idea was that this exception could be used for other uses besides just an unexpected final status but this is OK too.
All sessions include a logs field. Include logs in message If exception is in error. |
Please include Closes #66 when addressing a bug. That will close it automatically on merge. |
What is the name of the extra field? |
Lgtm! Merging |
Fail eagerly to wait for the idle status if we have reached a "final" status
wait_for_status()
towait_for_idle()
and adjust parameter list appropriately. If we ever need to wait for a status besides idle (seems unlikely?), then this can be refactored back out again.LivyUnexpectedError
if the Livy session goes into error or dead.