-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Use request context instead of background #10519
Use request context instead of background #10519
Conversation
This prevents goroutine leak: If background context were used then push operation would continue even if client aborted request by closing connection. [NO TESTS NEEDED] Signed-off-by: Matej Vasek <[email protected]>
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!
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: matejvasek, rhatdan The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
@@ -160,43 +145,50 @@ loop: // break out of for/select infinite loop | |||
} | |||
report.ID = e.Artifact.Digest.Encoded()[0:12] | |||
if err := enc.Encode(report); err != nil { | |||
errorWriter.Write([]byte(err.Error())) | |||
logrus.Warnf("Failed to json encode error %q", err.Error()) |
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.
Minor nit, but if this needs other changes, can you swap this to an Errorf
?
/lgtm |
/hold cancel |
This prevents goroutine leak:
If background context were used then push operation would continue even
if client aborted request by closing connection.
Signed-off-by: Matej Vasek [email protected]