Avoid changing global uncaught exception handler - #12076
Suthankan1 wants to merge 1 commit into
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review. 📝 WalkthroughWalkthrough
ChangesUncaught Exception Handler Preservation
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Suggested reviewers: Merge Risk: ⚪ Minimal · up to The Docker strategy no longer changes the JVM-wide uncaught-exception handler during endpoint polling, with regression coverage for that behavior. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
What changed
Disable Awaitility's uncaught-exception interception for the Docker client strategy socket check.
Awaitility otherwise temporarily replaces the JVM-wide default uncaught exception handler while
DockerClientProviderStrategychecks whether the Docker endpoint is reachable. This can intercept exceptions from unrelated threads.Using
dontCatchUncaughtExceptions()keeps the existing timeout and polling behavior while avoiding the global handler mutation.A regression test verifies that the JVM default uncaught exception handler remains unchanged while the Docker strategy check runs.
Testing
DockerClientProviderStrategyTest— RED before the fix, GREEN afterdockerclienttests passedThe full
:testcontainers:testrun also encountered unrelated Docker image download failures caused by local DNS/network resolution ofproduction.cloudfront.docker.com.Fixes #11483
Summary by CodeRabbit