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

Remove enum _UpdateType and retry fetching goal state #2018

Merged
merged 3 commits into from
Sep 24, 2020

Conversation

narrieta
Copy link
Member

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.

azurelinuxagent/common/protocol/wire.py Outdated Show resolved Hide resolved
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)
Copy link
Contributor

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

Copy link
Member Author

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)

Copy link
Member Author

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

Copy link
Member Author

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.

Copy link
Contributor

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?

Copy link
Member Author

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.

azurelinuxagent/common/protocol/goal_state.py Show resolved Hide resolved
kevinclark19a
kevinclark19a previously approved these changes Sep 23, 2020
Copy link
Contributor

@larohra larohra left a 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

@narrieta narrieta merged commit ddf8763 into Azure:develop Sep 24, 2020
@narrieta narrieta deleted the goal-state branch September 24, 2020 16:32
@narrieta narrieta restored the goal-state branch September 24, 2020 20:44
@narrieta narrieta deleted the goal-state branch September 24, 2020 20:45
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

Successfully merging this pull request may close these issues.

3 participants