-
Notifications
You must be signed in to change notification settings - Fork 5.8k
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: return the actual error when conn panic #18494
Conversation
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
@SunRunAway,Thanks for your review. |
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
@lysu,Thanks for your review. |
/merge |
/run-all-tests |
Codecov Report
@@ Coverage Diff @@
## master #18494 +/- ##
===========================================
Coverage 79.8641% 79.8641%
===========================================
Files 540 540
Lines 147046 147046
===========================================
Hits 117437 117437
Misses 20328 20328
Partials 9281 9281 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-3.0 in PR #18498 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-3.1 in PR #18499 |
Signed-off-by: ti-srebot <ti-srebot@pingcap.com>
cherry pick to release-4.0 in PR #18500 |
What problem does this PR solve?
Issue Number: close #18112
Problem Summary:
TiDB does not return the actual error when recovering a goroutine.
What is changed and how it works?
What's Changed:
How it Works:
As the title says.
Related changes
Check List
Tests
As the description in the related issue.
We'll get
ERROR 1105 (HY000): Out Of Memory Quota![conn_id=1]
after this commit.Side effects
N/A
Release note