Oh, I understood from Matz's initial suggestion that the exceptions should be chained, but I see now what he meant. I've applied the changes you suggested, @nobu. Thank you for clarifying, and for reviewing.marcper (Marcelo Pereira)
The exceptions are already being chained through `cause`, but I've just updated the tests to make this fact clearer. Indeed a new exception is created every time. Initially I looked for an API to simply update the backtrace on the exi...marcper (Marcelo Pereira)
Hello again. I've modified the patch to also link to the old exception via `cause`. Let me know if it's now a reasonable solution. Thanks, Marcelomarcper (Marcelo Pereira)
@sos4nt could you please assign this issue to @matz? This is a core class problem, and he is the listed maintainer for it. I can confirm the bug still exists in ruby 3.2.1 (2023-02-08 revision 31819e82c8) [x86_64-linux]marcper (Marcelo Pereira)
Pinging @matz. Sorry if I'm being annoying, but the contributor guide says I should send a reminder after a few weeks if there's no response. marcper (Marcelo Pereira)