-
Notifications
You must be signed in to change notification settings - Fork 1.3k
[ws-manager] Fix potential leak of request body #13957
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
started the job as gitpod-build-aledbf-fixl.1 because the annotations in the pull request description changed |
started the job as gitpod-build-aledbf-fixl.4 because the annotations in the pull request description changed |
You need to rebase. This will fix the failing build. |
/werft run 👍 started the job as gitpod-build-aledbf-fixl.6 |
@@ -95,28 +125,13 @@ func (p *WorkspaceReadyProbe) Run(ctx context.Context) WorkspaceProbeResult { | |||
continue | |||
} | |||
|
|||
if resp.StatusCode != http.StatusOK { | |||
resp.Body.Close() |
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.
Where is the potential leak? It looks like we only have 2 exit point, one is here, and another one is below, both case all have resp.Body.Close()
Description
Ensure we close the body of the request.
Modifies the change introduced in #13828
How to test
Release Notes
Werft options:
If enabled this will build
install/preview
Valid options are
all
,workspace
,webapp
,ide