-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
fix(tianmu): revert code, mv ret value from try block back to catch block. (#1532) #1555
fix(tianmu): revert code, mv ret value from try block back to catch block. (#1532) #1555
Conversation
…lock [summary] The logic of this modification is as follows: Previously, set ret action has been moved to try block, which is not efficient because every time we do truncate success, ret will be setted to 1. This time we will move the set ret action back to catch block, which will only trigged when truncate failed.
Thanks for the contribution! Please review the labels and make any necessary changes. |
@Dysprosium0626 Thanks for your contribution, and pls sign the CLA at first. |
@RingsC thanks, I have completed signed the CLA |
Codecov ReportPatch coverage has no change and project coverage change:
Additional details and impacted files@@ Coverage Diff @@
## stonedb-5.7-dev #1555 +/- ##
===================================================
- Coverage 45.14% 45.06% -0.09%
===================================================
Files 1999 1999
Lines 413931 413931
===================================================
- Hits 186873 186533 -340
- Misses 227058 227398 +340
... and 86 files with indirect coverage changes Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
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
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
The logic of this modification is as follows:
Previously, set ret action has been moved to try block, which is not efficient because every time we do truncate success, ret will be setted to 1. This time we will move the set ret action back to catch block, which will only trigged when truncate failed.
Summary about this PR
Issue Number: close #1532
Tests Check List
Changelog
Documentation