Assert not same executor when completing future #108934
Merged
Commits on May 23, 2024
-
Assert not same executor when completing future
A common deadlock pattern is waiting and completing a future on the same executor. This only works until the executor is fully depleted of threads. Now assert that waiting for a future to be completed and the completion happens on different executors.
-
-
-
-
-
Commits on May 24, 2024
-
Add and use UnsafePlainActionFuture
Too many issues to fix in one PR, add a class that is used where we rely on notifying on same thread to at least have visibility.
-
-
-
-
-
-
-
-
-
Commits on May 25, 2024
-
Merge remote-tracking branch 'origin/main' into assert_not_same_execu…
…tor_when_completing_future
-
-
Commits on May 26, 2024
Commits on May 28, 2024
-
-
Merge remote-tracking branch 'origin/main' into assert_not_same_execu…
…tor_when_completing_future
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.