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

server: fix potential goroutine leak when kill connection (#13051) #13252

Merged
merged 3 commits into from
Nov 8, 2019

Conversation

SunRunAway
Copy link
Contributor

cherry-pick #13051


What problem does this PR solve?

Fix #13050

What is changed and how it works?

Check List

Tests

  • Unit test (covered by TestShutDown)

Code changes

  • None

Side effects

  • None

Related changes

  • None

Release note

  • None

@tiancaiamao
Copy link
Contributor

LGTM

@tiancaiamao tiancaiamao added the status/LGT1 Indicates that a PR has LGTM 1. label Nov 8, 2019
Copy link
Contributor

@lysu lysu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zz-jason zz-jason added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Nov 8, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Nov 8, 2019

Your auto merge job has been accepted, waiting for 13251

@sre-bot
Copy link
Contributor

sre-bot commented Nov 8, 2019

/run-all-tests

@sre-bot sre-bot merged commit 57d29f4 into pingcap:release-2.1 Nov 8, 2019
@SunRunAway SunRunAway deleted the release-2.1 branch November 8, 2019 13:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/server status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants