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

cleanups: fix linter issues 20231026 #237

Merged
merged 5 commits into from
Oct 26, 2023

Conversation

ffromani
Copy link
Collaborator

the linter run revealed a good bit of potential issues.
Please check each commit for context and rationale

make sure to use the up-to-date function,
honoring context and make it cancellable.
Not intended change in behavior.

Signed-off-by: Francesco Romani <[email protected]>
cosmetic change only

Signed-off-by: Francesco Romani <[email protected]>
make sure to bubble up error, and don't leak
response body. This code should run only once
per `deployer` execution, but still let's not
leak resources if we can help it.

Signed-off-by: Francesco Romani <[email protected]>
make sure we bail out on error if fail to set
the field.

Signed-off-by: Francesco Romani <[email protected]>
make sure to bubble up errors if we fail to teardown the proxy.
We should not leak processes.

Signed-off-by: Francesco Romani <[email protected]>
@ffromani ffromani merged commit d967eec into k8stopologyawareschedwg:main Oct 26, 2023
3 checks passed
@ffromani ffromani deleted the fix-lint-20231026 branch October 26, 2023 09:49
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.

1 participant