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

Cherry pick v3.0.1 #4027

Merged
merged 3 commits into from
Mar 14, 2022
Merged

Cherry pick v3.0.1 #4027

merged 3 commits into from
Mar 14, 2022

Conversation

Aiee
Copy link
Contributor

@Aiee Aiee commented Mar 14, 2022

What type of PR is this?

  • bug
  • feature
  • enhancement

What problem(s) does this PR solve?

Issue(s) number:

Description:

How do you solve it?

Special notes for your reviewer, ex. impact of this fix, design document, etc:

Checklist:

Tests:

  • Unit test(positive and negative cases)
  • Function test
  • Performance test
  • N/A

Affects:

  • Documentation affected (Please add the label if documentation needs to be modified.)
  • Incompatibility (If it breaks the compatibility, please describe it and add the label.)
  • If it's needed to cherry-pick (If cherry-pick to some branches is required, please label the destination version(s).)
  • Performance impacted: Consumes more CPU/Memory

Release notes:

Please confirm whether to be reflected in release notes and how to describe:

ex. Fixed the bug .....

darionyaphet and others added 3 commits March 14, 2022 20:37
Co-authored-by: Sophie <84560950+Sophie-Xie@users.noreply.github.com>
…inc#4021)

* Update error message

* Do clientAddr check before FLAGS_enable_authorize check

* Fix typo
@Aiee Aiee added the ready-for-testing PR: ready for the CI test label Mar 14, 2022
@yixinglu yixinglu merged commit 2e938c7 into vesoft-inc:v3.0.1 Mar 14, 2022
@Aiee Aiee deleted the v3.0.1 branch March 14, 2022 13:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready-for-testing PR: ready for the CI test
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants