-
Notifications
You must be signed in to change notification settings - Fork 8.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
bugfix: The TCC aspect does not handle internal invocation exceptions and directly throws them externally. #6090
bugfix: The TCC aspect does not handle internal invocation exceptions and directly throws them externally. #6090
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## 2.x #6090 +/- ##
============================================
+ Coverage 49.23% 49.27% +0.03%
- Complexity 4790 4799 +9
============================================
Files 913 913
Lines 31677 31685 +8
Branches 3824 3825 +1
============================================
+ Hits 15597 15613 +16
+ Misses 14535 14523 -12
- Partials 1545 1549 +4
|
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.
建议补充一个测试用例,证明其不再是runtimeexception
It is recommended to add a test case to prove that it is no longer a RuntimeException
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.
others is ok
# Conflicts: # changes/en-us/2.x.md # changes/zh-cn/2.x.md
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
# Conflicts: # changes/en-us/2.x.md # changes/zh-cn/2.x.md
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
… and directly throws them externally. (apache#6090)
2.x版本中支持去spring能力,对切面部分做了重构处理,如果tcc一二阶段rpc调用过程出现异常,会多加一层框架内部异常,部分业务之前会严格校验rpc调用产生的原生异常,这样会导致原判断失效不成立。为了兼容做处理,直接将异常抛出。
fixes #6084