-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
optimize: judging xid status to avoid repeated processing #2597
Conversation
Codecov Report
@@ Coverage Diff @@
## develop #2597 +/- ##
=============================================
- Coverage 50.91% 50.78% -0.14%
- Complexity 2814 2815 +1
=============================================
Files 558 558
Lines 17936 17936
Branches 2127 2097 -30
=============================================
- Hits 9132 9108 -24
- Misses 7934 7935 +1
- Partials 870 893 +23 |
Codecov Report
@@ Coverage Diff @@
## develop #2597 +/- ##
==========================================
Coverage 50.60% 50.60%
- Complexity 3101 3102 +1
==========================================
Files 599 599
Lines 19498 19499 +1
Branches 2404 2404
==========================================
+ Hits 9866 9867 +1
Misses 8641 8641
Partials 991 991
|
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
@jsbxyyx @l81893521 PTAL |
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
Ⅰ. Describe what this PR did
judging xid status to avoid repeated processing
transactionPropagationIntercepter with seataHandlerInterceptor conflict
Ⅱ. Does this pull request fix one issue?
Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
relevance: alibaba/spring-cloud-alibaba#1352