-
Notifications
You must be signed in to change notification settings - Fork 372
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
Remove enum _UpdateType and retry fetching goal state #2018
Conversation
return | ||
except Exception as exception: | ||
# We don't log the error here since fetching the goal state is done every few seconds | ||
raise ProtocolError(msg="Error fetching goal state", inner=exception) |
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.
Would it be useful to add a traceback here? Might be useful in figuring out what exactly failed when trying to fetch GS
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.
I thought you were adding the traceback to error messages? (one way to do that could be in the conversion to string of the base class for exceptions)
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.
btw - since this is just raising the exception, the traceback shouln't be added here, but in whoever handles the exception
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.
and another note:
one way to do that could be in the conversion to string of the base class for exceptions)
may lead to bad (but useful) formatting. An alternative would be to create a function in the logger to log an exception. That function could also add traceback for the inner exceptions.
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.
I thought you were adding the traceback to error messages?
I was primarily talking about doing it on a case to case basis, but I like your idea better of adding it for every error.
An alternative would be to create a function in the logger to log an exception.
That would be useful for sure, maybe reuse the logger.error? But anyways not sure when I'll get time to work on that. For now do you wanna add the trace here until we have a better solution in place?
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.
The trace should not be added here, that should be done at the place where the exception is handled.
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.
1 minor comment but else LGTM
Removing enum _UpdateType simplifies the code a little bit.
The retry logic fetching goal state is not needed; the underlying http APIs aready handle retry.