-
Notifications
You must be signed in to change notification settings - Fork 10.1k
Update calls to StateMgr method to use diagnostics more conventionally #37597
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
Conversation
|
I can't run the kubernetes tests using the usual method, as I think ToB has removed docker from my laptop.
|
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.
lgtm!
Thanks! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Follow up to #37589. In that case, the interface defining the StateMgr method was updated to return diagnostics instead of errors, and something went wrong when that change was pulled into a long-lived feature branch.
This PR changes that code and other examples of calling code to handle diagnostics more conventionally:
nil
values, inspect for errorserror
representation of the diagnostics where calling code previously used errors to make test failure messages or return errors to users.Target Release
N/A
Rollback Plan
Changes to Security Controls
Are there any changes to security controls (access controls, encryption, logging) in this pull request? If so, explain.
CHANGELOG entry