Capture backtraces for UnexpectedResult messages #35

Activity

1. bougyman

   added 5 commits that reference this issue on Aug 16, 2025

   fix: #35 - Limits the backtrace to 4 lines in our exceptions

   This issue will close once commit c8b88a4 is merged into the 'main' branch.

   c8b88a4

   fix: #35 - Adds test for backtrace truncation

   This issue will close once commit 1d8f611 is merged into the 'main' branch.

   1d8f611

   chore: #35 Merge branch 'issue-35' of github.com:rubyists/leopard int…

   ...

   This issue will close once commit 9585bbc is merged into the 'main' branch.

   9585bbc

   fix: #35 - Adds nil check in case backtrace is empty

   This issue will close once commit e20d7f2 is merged into the 'main' branch.

   e20d7f2

   fix: #35 - Do not add a truncate message if we did not truncate it

   This issue will close once commit 027fcd0 is merged into the 'main' branch.

   027fcd0
2. bougyman

   closed this as completedin df0fee8on Aug 16, 2025
3. Copilot

   added a commit that references this issue on Apr 16, 2026

   fix: #35 - Limits the backtrace to 4 lines in our exceptions (#36)

   ...

   This issue will close once commit df0fee8 is merged into the 'main' branch.

   df0fee8