-
Notifications
You must be signed in to change notification settings - Fork 26.4k
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 triple client stream executor #13178
Fix triple client stream executor #13178
Conversation
|
Codecov Report
@@ Coverage Diff @@
## 3.2 #13178 +/- ##
============================================
- Coverage 69.38% 69.36% -0.02%
Complexity 2 2
============================================
Files 1648 1648
Lines 68693 68694 +1
Branches 10014 10012 -2
============================================
- Hits 47661 47649 -12
- Misses 16438 16454 +16
+ Partials 4594 4591 -3 see 43 files with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
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
* add ping pong for tri protocol * add ping pong for tri protocol * add ping pong for tri protocol * add ping pong for tri protocol
This reverts commit 5a3be17.
…t-executor # Conflicts: # dubbo-remoting/dubbo-remoting-netty4/src/main/java/org/apache/dubbo/remoting/transport/netty4/NettyConnectionClient.java
Kudos, SonarCloud Quality Gate passed! |
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
What is the purpose of the change
At present, executor of triple client uses wrong ThreadFactory and ThreadPool, default client thread pool is CachedThreadPool.
For example:
Brief changelog
Verifying this change
Checklist