Skip to content

Conversation

@ym0506
Copy link

@ym0506 ym0506 commented Feb 3, 2026

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:

  • Added a regression test to ensure the strategy probing code path includes dontCatchUncaughtExceptions, and to validate Awaitility does not intercept uncaught exceptions from other threads when configured accordingly.

@ym0506 ym0506 requested a review from a team as a code owner February 3, 2026 07:41
@ym0506
Copy link
Author

ym0506 commented Feb 3, 2026

CI workflows are awaiting maintainer approval (fork PR). Could a maintainer approve the workflows so required checks can run?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Running testcontainers temporarily changes global uncaught exception handler

1 participant