-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: optimization of adapter code #551
Conversation
Codecov Report
@@ Coverage Diff @@
## master #551 +/- ##
============================================
+ Coverage 87.71% 87.73% +0.02%
+ Complexity 469 466 -3
============================================
Files 52 52
Lines 1889 1884 -5
Branches 167 163 -4
============================================
- Hits 1657 1653 -4
+ Misses 192 191 -1
Partials 40 40
|
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.
@dgarus one suggestion, please, check
CompletableFuture.runAsync(this.updateOther(packages, res)), | ||
CompletableFuture.runAsync(this.updateFilelist(packages, res)) | ||
); | ||
Append.setPrimaryPckg(temp, res, primary).run(); |
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.
Append.setPrimaryPckg(temp, res, primary).run()
can also be run in parallel
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.
We also should use this thread.
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.
hm, I see, maybe we change method return type to void
? Runnable is not required and seems confusing in such implementation
part of #550