Disable Awaitility uncaught-exception catching (fixes #11483) #11484
+99
−0
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.
Fixes #11483
Testcontainers uses Awaitility in a few internal wait loops (e.g. during Docker client strategy probing, image pull retry, container start/port checks). Awaitility’s default behavior can temporarily install a global default uncaught exception handler, which may intercept uncaught exceptions from unrelated threads and can lead to surprising/flaky test behavior.
This change explicitly disables that behavior by adding
.dontCatchUncaughtExceptions()to all internal Awaitility usages.Tests:
dontCatchUncaughtExceptions, and to validate Awaitility does not intercept uncaught exceptions from other threads when configured accordingly.