-
Notifications
You must be signed in to change notification settings - Fork 695
Replacing CompletableFuture.supplyAsync() with fixed thread pool executor. CompletableFuture.supplyAsync() uses the common ForkJoinPool, which may not have enough threads. #7908
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
Merged
Merged
Changes from 1 commit
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
I think with this change the test would continue too quickly.
The goal of this line is to wait until the tasks have started.
await().untilAssertedrepeatedly runs() -> assertThat(service.getNumberOfCurrentExecutions()).isEqualTo(2)until it succeeds (or times out).Changing the assertion to
.isLessThanOrEqualTo(2)would make the test continue before both tasks have started, which I think is not what we want.Do you see it time out? Perhaps we need to give it some more time before it gives up waiting for both tasks to start?
Uh oh!
There was an error while loading. Please reload this page.
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.
Hi @raboof, thank you for your review. I agree, it's better to keep the
isEqualTo(2). I pushed a new fix replacing theCompletableFuture.supplyAsync()with fixed thread pool executor.CompletableFuture.supplyAsync()uses the common ForkJoinPool, which may not have enough threads for all concurrent executions which will causeawait().assertThat(service.getNumberOfCurrentExecutions()).isEqualTo(2)to timeout.