-
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: handle clients without authplugin support (#27931) #28734
server: handle clients without authplugin support (#27931) #28734
Conversation
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/run-all-tests |
@dveeden you're already a collaborator in bot's repo. |
/run-check_dev |
@dveeden The test failures are caused by us porting tests in master to testify, but release-5.2 uses testkit:
|
@dveeden Please address the comment. |
Signed-off-by: ti-srebot <[email protected]>
98c42f9
to
afddb6a
Compare
/assign @morgo @tiancaiamao |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: afddb6a
|
@ti-srebot: Your PR was out of date, I have automatically updated it for you. At the same time I will also trigger all tests for you: /run-all-tests If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository. |
cherry-pick #27931 to release-5.2
You can switch your code base to this Pull Request by using git-extras:
# In tidb repo: git pr https://github.com/pingcap/tidb/pull/28734
After apply modifications, you can push your change to this PR via:
What problem does this PR solve?
Issue Number: close #27855
Problem Summary:
Old (MySQL 5.1 and before) clients that don't send authentication plugin info in the login packet were having issues authenticating and/or got an incorrect error message
What is changed and how it works?
mysql.ClientPluginAuth
inresp.Capability
.Check List
Tests
Documentation
Release note