Fix NullPointerException in Exception Replay#11976
Conversation
fingerprint can be null in rare occasions
There was a problem hiding this comment.
More details
Null fingerprint check correctly handles a rare but real edge case in exception replay where circular exception chains or digest algorithm failures cause Fingerprinter.fingerprint() to return null. The fix is minimal, focused, and prevents a NullPointerException without changing behavior for normal exceptions. Existing tests (FingerprinterTest.innerInfiniteLoop) confirm this code path is reachable.
📊 Validated against 4 scenarios · Open Bits AI session
🤖 Datadog Autotest · Commit 1910776 · What is Autotest? · Any feedback? Reach out in #autotest
|
Bits Code status: ✅ Done Comment @DataDog to request changes |
|
🎯 Code Coverage (details) 🔗 Commit SHA: 1910776 | Docs | Datadog PR Page | Give us feedback! |
🟢 Java Benchmark SLOs — All performance SLOs passed
PR vs. master results
Commit: Load and DaCapo benchmarks can be triggered manually in the GitLab pipeline. Results will appear in the Benchmarking Platform UI after completion. |
|
/merge |
|
View all feedbacks in Devflow UI.
The expected merge time in
|
45a9d0e
into
master
What Does This Do
fingerprint can be null in rare occasions
Motivation
Additional Notes
Contributor Checklist
type:and (comp:orinst:) labels in addition to any other useful labelsclose,fix, or any linking keywords when referencing an issueUse
solvesinstead, and assign the PR milestone to the issueJira ticket: DEBUG-5675