You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When CompletableFuture.thenComposeAsync is called without specifying executor the task runs on default thread pool which is incorrect.
Instead, always call overload that explicitly takes executor.
To Reproduce
This was recently observed in longevity test.
Screenshots
Below is list of relevant calls
Additional information
Add any other information about the problem here, including the root cause if known.
The text was updated successfully, but these errors were encountered:
Describe the bug
When CompletableFuture.thenComposeAsync is called without specifying executor the task runs on default thread pool which is incorrect.
Instead, always call overload that explicitly takes executor.
To Reproduce
This was recently observed in longevity test.
Screenshots
Below is list of relevant calls
Additional information
Add any other information about the problem here, including the root cause if known.
The text was updated successfully, but these errors were encountered: