-
Notifications
You must be signed in to change notification settings - Fork 883
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
[KYUUBI #2156][FOLLOWUP] Fix configuration format in document #2165
Conversation
If possible, when you touch the document, would you please build the document in local and paste the preview screenshot in your PR description? |
Codecov Report
@@ Coverage Diff @@
## master #2165 +/- ##
=========================================
Coverage 61.31% 61.31%
Complexity 117 117
=========================================
Files 321 321
Lines 15515 15515
Branches 1992 1992
=========================================
Hits 9513 9513
Misses 5192 5192
Partials 810 810 Continue to review full report at Codecov.
|
Thanks, merging master/branch-1.5 |
### _Why are the changes needed?_ fix #2157 cofiguration format error ### _How was this patch tested?_ - [ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible - [ ] Add screenshots for manual tests if appropriate - [x] [Run test](https://kyuubi.apache.org/docs/latest/develop_tools/testing.html#running-tests) locally before make a pull request Closes #2165 from jiaoqingbo/2156-followup. Closes #2156 9862ddb [jiaoqingbo] [KYUUBI #2156][FOLLOWUP] Fix configuration format in document 47157c5 [jiaoqingbo] Merge branch 'master' into 2156-followup 9c89c08 [jiaoqingbo] [KYUUBI #2156][FOLLOWUP]fix cofiguration format 4608432 [jiaoqingbo] Merge branch 'master' into 2156 96a22e5 [jiaoqingbo] add link to doc dc11a21 [jiaoqingbo] [KYUUBI #2156] Change log to reflect exactly why getting token failed Authored-by: jiaoqingbo <1178404354@qq.com> Signed-off-by: Cheng Pan <chengpan@apache.org>
Why are the changes needed?
fix #2157 cofiguration format error
How was this patch tested?
Add some test cases that check the changes thoroughly including negative and positive cases if possible
Add screenshots for manual tests if appropriate
Run test locally before make a pull request